Wellness aggregator

ABSTRACT

The present disclosure relates to aggregating and sharing wellness data. The wellness data can be received by a user device from any number of sensors external or internal to the user device, from a user manually entering the wellness data, or from other users or entities. The user device can securely store the wellness data on the user device and transmit the wellness data to be stored on a remote database. A user of the device can share some or all of the wellness data with friends, relatives, caregivers, healthcare providers, or the like. The user device can further display a user&#39;s wellness data in an aggregated view of different types of wellness data. Wellness data of other users can also be viewed if authorizations from those users have been received.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. non-provisional patent application Ser. No. 17/735,395, entitled “WELLNESS AGGREGATOR,” filed May 3, 2022, which is a continuation of U.S. non-provisional patent application Ser. No. 16/820,383, entitled “WELLNESS AGGREGATOR,” filed Mar. 16, 2020, which is a continuation of U.S. non-provisional patent application Ser. No. 14/732,773, entitled “WELLNESS AGGREGATOR”, filed Jun. 7, 2015, which is a continuation-in-part of International Application PCT/US2013/073195, entitled “WELLNESS AGGREGATOR”, filed Dec. 4, 2013, and a continuation-in-part of International Application PCT/US2015/032474, entitled “WELLNESS AGGREGATOR”, filed May 26, 2015, which claims priority to U.S. Provisional Patent Application Ser. No. 62/129,945, entitled “WELLNESS AGGREGATOR”, filed Mar. 8, 2015, and U.S. Provisional Patent Application Ser. No. 62/006,032, entitled “WELLNESS AGGREGATOR”, filed May 30, 2014. This application is a continuation-in-part of U.S. non-provisional patent application Ser. No. 14/599,424, entitled “WELLNESS AGGREGATOR”, filed Jan. 16, 2015, which claims priority to U.S. Provisional Patent Application Ser. No. 62/006,032, entitled “WELLNESS AGGREGATOR”, filed May 30, 2014. The content of these applications is hereby incorporated by reference herein.

This application relates to U.S. Provisional Patent Application Ser. No. 62/006,031, entitled “MANAGING USER INFORMATION,” filed May 30, 2014, the content of which is hereby incorporated by reference herein.

FIELD

The following disclosure relates generally to data management and, more specifically, to aggregating and sharing wellness data.

BACKGROUND

Approximately 133 million Americans currently suffer from at least one chronic condition. This number is expected to rise to approximately 165 million by the year 2020. As a result, the cost of healthcare in the United States is expected to increase dramatically. Attempts have been made to improve the health of individuals by providing them with tools to monitor and, track their wellness data. Wellness data can generally include any type of data associated with a person's health, such as their weight, heart rate, blood pressure, blood glucose level, medication compliance, activity level, or the like. Users can monitor their wellness using devices, such as blood pressure cuffs, blood glucose monitors, electrocardiograms, step counters, and the like. Software applications (e.g., Apps) associated with each of these devices have also been developed to allow users to track their wellness data over time. While each application can be used to view useful information about a user's health, current applications are limited in their ability to allow users to store, view, and share wellness data collected by different devices.

SUMMARY

The present disclosure relates to processes for aggregating and sharing wellness data. One example process can include causing a display of an aggregated view of a plurality of types of wellness data, wherein the aggregated view comprises a plurality of partitions, each partition of the plurality of partitions associated with a type of the plurality of types of wellness data; receiving a selection of a partition of the plurality of partitions; and causing a display of an expanded view of the selected partition of the plurality of partitions.

An example process can include display, on the display screen, a graph comprising: a first data-set representation of a first data set in which a first dependent variable varies as an independent variable changes and a second data-set representation of a second data set in which a second dependent variable varies as the independent variable changes, wherein the first data-set representation comprises a plurality of indicators corresponding to values of the dependent variables of the first data-set representation, wherein the second data-set representation is associated with a range of vertical positions within the graph, wherein the dependent variables of the first data set are chosen from a set of discrete values; detect, at a respective location on the display screen, a user input; in response to detecting the user input: in accordance with a determination that the respective location corresponds to an indicator of the plurality of indicators, display, on the display screen, an indication that the first data-set representation has been selected; and in accordance with a determination that the respective location is within the range of vertical positions associated with the second data-set representation, but away from the plurality of indicators, display, on the display screen, an indication that the second data-set representation has been selected.

Devices and non-transitory computer-readable storage media for performing these processes are also provided.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screen in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.

FIG. 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

FIG. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with some embodiments.

FIG. 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.

FIG. 6 illustrates a block diagram of an example system for aggregating wellness data according to various examples.

FIG. 7 illustrates a block diagram of an example system for sharing wellness data according to various examples.

FIG. 8 illustrates an example process for authorizing and pushing wellness data to authorized other users according to various examples.

FIG. 9 illustrates an example process for authorizing users to pull wellness data according to various examples.

FIG. 10 illustrate example interfaces for displaying aggregated wellness data according to various examples.

FIG. 11 illustrates example interfaces for displaying aggregated wellness data according to various examples.

FIG. 12 illustrates example interfaces for displaying aggregated wellness data according to various examples.

FIG. 13 illustrates example interfaces for displaying aggregated wellness data according to various examples.

FIG. 14 illustrates example interfaces for displaying aggregated wellness data according to various examples.

FIG. 15 illustrates example interfaces for displaying aggregated wellness data according to various examples.

FIG. 16 illustrates an example process for displaying aggregated wellness data according to various examples.

FIG. 17 illustrates an example interface for displaying aggregated wellness data according to various examples.

FIG. 18 illustrates an example process for displaying aggregated wellness data according to various examples.

FIG. 19 illustrates an example interface for displaying aggregated wellness data of other users according to various examples.

FIG. 20 illustrates another example interface for displaying aggregated wellness data of other users according to various examples.

FIG. 21 illustrates an example process for displaying aggregated wellness data of other users according to various examples.

FIG. 22 illustrates example interfaces for displaying wellness or non-wellness data according to various examples.

FIG. 23 illustrates example interfaces for displaying wellness or non-wellness data according to various examples.

FIG. 24 illustrates example interfaces for displaying wellness or non-wellness data according to various examples.

FIGS. 25A and 25B illustrate example interfaces for displaying wellness or non-wellness data according to various examples.

FIG. 26 illustrates example interfaces for displaying wellness or non-wellness data according to various examples.

FIG. 27 illustrates an example process for displaying wellness or non-wellness data according to various examples.

FIG. 28 illustrates example interfaces for displaying wellness or non-wellness data according to various examples.

FIG. 29 illustrates example interfaces for displaying wellness or non-wellness data according to various examples.

FIG. 30 illustrates example interfaces for displaying wellness or non-wellness data according to various examples.

FIG. 31 illustrates example interfaces for displaying wellness or non-wellness data according to various examples.

FIG. 32 illustrates example interfaces for displaying wellness or non-wellness data according to various examples.

FIG. 33 illustrates example interfaces for displaying wellness or non-wellness data according to various examples.

FIG. 34 illustrates example interfaces for displaying wellness or non-wellness data according to various examples.

FIG. 35 illustrates example interfaces for displaying wellness or non-wellness data according to various examples.

FIG. 36 illustrates example interfaces for displaying wellness or non-wellness data according to various examples.

FIG. 37 illustrates example interfaces for displaying wellness or non-wellness data according to various examples.

FIGS. 38A and 38B illustrate an example process for managing and displaying wellness or non-wellness data according to various examples.

FIG. 39 illustrates example interfaces for displaying emergency medical information according to various examples.

FIG. 40 illustrates example interfaces for displaying emergency medical information according to various examples.

FIG. 41 illustrates example interfaces for displaying emergency medical information according to various examples.

FIG. 42 illustrates example interfaces for displaying emergency medical information according to various examples.

FIG. 43 illustrates example interfaces for displaying emergency medical information according to various examples.

FIG. 44 illustrates example interfaces for displaying emergency medical information according to various examples.

FIG. 45 illustrates an example process for displaying emergency medical information according to various examples.

FIG. 46 illustrates an example computing system for aggregating and sharing wellness data according to various examples.

FIG. 47 illustrates a functional block diagram of an electronic device configured to display wellness or non-wellness data according to various examples.

FIG. 48 illustrates a functional block diagram of an electronic device configured to manage and display wellness or non-wellness data according to various examples.

FIG. 49 illustrates a functional block diagram of an electronic device configured to display emergency medical information according to various examples.

FIG. 50 illustrates a functional block diagram of an electronic device configured to display wellness or non-wellness data according to various examples.

FIG. 51 illustrates a functional block diagram of an electronic device configured to display wellness or non-wellness data according to various examples.

FIG. 52 illustrates a functional block diagram of an electronic device configured to display wellness or non-wellness data according to various examples.

FIG. 53 illustrates a functional block diagram of an electronic device configured to display wellness or non-wellness data according to various examples.

FIG. 54 illustrates a functional block diagram of an electronic device configured to display wellness or non-wellness data according to various examples.

FIGS. 55A and 55B illustrate exemplary interfaces for displaying wellness or non-wellness data according to various examples.

FIGS. 56A-56D illustrate exemplary interfaces for displaying wellness or non-wellness data according to various examples.

FIGS. 57A-57D illustrate exemplary interfaces for displaying wellness or non-wellness data according to various examples.

FIGS. 58A-58D illustrate exemplary interfaces for displaying wellness or non-wellness data according to various examples.

FIGS. 59A-59D illustrate exemplary interfaces for displaying wellness or non-wellness data according to various examples.

FIGS. 60A-60D illustrate exemplary interfaces for displaying wellness or non-wellness data according to various examples.

FIGS. 61A-61D illustrate exemplary interfaces for displaying wellness or nonwellness data according to various examples.

FIGS. 62A and 62B illustrate exemplary interfaces for displaying wellness or nonwellness data according to various examples.

FIG. 63 illustrates an example interface for inputting wellness or non-wellness data according to various examples.

FIG. 64A-64F illustrate exemplary interfaces for displaying wellness or non-wellness data according to various examples.

FIGS. 65A-65C illustrate exemplary interfaces for displaying wellness or non-wellness data according to various examples.

FIGS. 66A and 66B illustrate exemplary interfaces for displaying wellness or nonwellness data according to various examples.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.

The present disclosure relates to aggregating and sharing wellness data. The wellness data can be received by a user device from any number of sensors external or internal to the user device, from a user manually entering the wellness data, or from other users or entities. The user device can securely store the wellness data on the user device and transmit the wellness data to be stored on a remote database. A user of the device can share some or all of the wellness data with friends, relatives, caregivers, healthcare providers, or the like. The user device can further display a user's wellness data in an aggregated view of different types of wellness data. For example, the aggregated view can include a set of partitions, where each partition corresponds to a different type of wellness data. Wellness data of other users can also be viewed if authorizations from those users have been received. In some examples, the partitions can be displayed as having the appearance and associated animations of a stack of cards, where each card corresponds to a different partition (and thus, a different type of wellness data). In this view of stacked cards, each card can display a partial view of a portion of its corresponding wellness data. When the user selects one of the cards, a first expanded view of the selected card including at least one of first reconfigured data, additional data, or an expanded view of the original data can be displayed. A second expanded view of the selected card can be displayed in response to a change in the orientation of the user device. The second expanded view can include at least one of second reconfigured data, additional data, or an expanded view of the original data can be displayed. In one example, the second expanded view can include a graph of the wellness data over time.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description of exemplary devices for performing the techniques for sharing wellness data. FIGS. 10-15, 17, 19-20, 22-26, 28-37, 39-44, and 55-66 illustrate exemplary user interfaces for sharing wellness data. The user interfaces in the figures are also used to illustrate the processes described below, including the processes in FIGS. 8, 9, 16, 18, 21, 27, 38A-B, and 45.

Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.

The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a”, “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).

In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.

The device may support a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.” Device 100 includes memory 102 (which optionally includes one or more computer-readable storage mediums), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting intensity of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.

It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in FIG. 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application-specific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums. The computer-readable storage mediums may be tangible and non-transitory. Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 may control access to memory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 may be implemented on a single chip, such as chip 104. In some other embodiments, they may be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSDPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212, FIG. 2 ). The headset jack provides an interface between audio circuitry 110 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2 ) optionally include an up/down button for volume control of speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206, FIG. 2 ).

A quick press of the push button may disengage a lock of touch screen 112 or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) may turn power to device 100 on or off. The user may be able to customize a functionality of one or more of the buttons. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 112 and display controller 156 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may be analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the various components. Power system 162 may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to optical sensor controller 158 in I/O subsystem 106. Optical sensor 164 may include charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor 164 receives light from the environment, projected through one or more lenses, and converts the light to data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 may capture still images or video. In some embodiments, an optical sensor is located on the back of device 100, opposite touch screen display 112 on the front of the device so that the touch screen display may be used as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user's image may be obtained for video conferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of optical sensor 164 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor 164 may be used along with the touch screen display for both video conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I/O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternately, proximity sensor 166 may be coupled to input controller 160 in I/O subsystem 106. Proximity sensor 166 may perform as described in U.S. patent application Ser. No. 11/241,839, “Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “Proximity Detector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and Ser. No. 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 in I/O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates tactile outputs on device 100 that are capable of being sensed by a user of device 100. In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device 100) or laterally (e.g., back and forth in the same plane as a surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternately, accelerometer 168 may be coupled to an input controller 160 in I/O subsystem 106. Accelerometer 168 may perform as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device 100 optionally includes, in addition to accelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 ) stores device/global internal state 157, as shown in FIGS. 1A and 3 . Device/global internal state 157 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and location information concerning the device's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.

In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).

Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including ,without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).

GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets of instructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact         list);     -   Telephone module 138;     -   Video conference module 139;     -   E-mail client module 140;     -   Instant messaging (IM) module 141;     -   Workout support module 142;     -   Camera module 143 for still and/or video images;     -   Image management module 144;     -   Video player module;     -   Music player module;     -   Browser module 147;     -   Calendar module 148;     -   Widget modules 149, which may include one or more of: weather         widget 149-1, stocks widget 149-2, calculator widget 149-3,         alarm clock widget 149-4, dictionary widget 149-5, and other         widgets obtained by the user, as well as user-created widgets         149-6;     -   Widget creator module 150 for making user-created widgets 149-6;     -   Search module 151;     -   Video and music player module 152, which merges video player         module and music player module;     -   Notes module 153;     -   Map module 154; and/or     -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 may be used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.

In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that may be downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. For example, video player module may be combined with music player module into a single module (e.g., video and music player module 152, FIG. 1A). In some embodiments, memory 102 may store a subset of the modules and data structures identified above. Furthermore, memory 102 may store additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.

Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.

Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.

Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected may correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected may be called the hit view, and the set of events that are recognized as proper inputs may be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.

Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 may utilize or call data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information may also include speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.

Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers may interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.

FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100. In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes input/output (I/O) interface 330 comprising display 340, which is typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, tactile output generator 357 for generating tactile outputs on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A), sensors 359 (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices remotely located from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A), or a subset thereof. Furthermore, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The above-identified modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 may store a subset of the modules and data structures identified above. Furthermore, memory 370 may store additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces that may be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces may be implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),         such as cellular and Wi-Fi signals;     -   Time 404;     -   Bluetooth indicator 405;     -   Battery status indicator 406;     -   Tray 408 with icons for frequently used applications, such as:         -   Icon 416 for telephone module 138, labeled “Phone,” which             optionally includes an indicator 414 of the number of missed             calls or voicemail messages;         -   Icon 418 for e-mail client module 140, labeled “Mail,” which             optionally includes an indicator 410 of the number of unread             e-mails;         -   Icon 420 for browser module 147, labeled “Browser;” and         -   Icon 422 for video and music player module 152, also             referred to as iPod (trademark of Apple Inc.) module 152,             labeled “iPod;” and     -   Icons for other applications, such as:         -   Icon 424 for IM module 141, labeled “Messages;”         -   Icon 426 for calendar module 148, labeled “Calendar;”         -   Icon 428 for image management module 144, labeled “Photos;”         -   Icon 430 for camera module 143, labeled “Camera;”         -   Icon 432 for online video module 155, labeled “Online             Video;”         -   Icon 434 for stocks widget 149-2, labeled “Stocks;”         -   Icon 436 for map module 154, labeled “Maps;”         -   Icon 438 for weather widget 149-1, labeled “Weather;”         -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”         -   Icon 442 for workout support module 142, labeled “Workout             Support;”         -   Icon 444 for notes module 153, labeled “Notes;” and         -   Icon 446 for a settings application or module, labeled             “Settings,” which provides access to settings for device 100             and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A are merely exemplary. For example, icon 422 for video and music player module 152 may optionally be labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g., touch screen display 112). Device 300 also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors 357) for detecting intensity of contacts on touch-sensitive surface 451 and/or one or more tactile output generators 359 for generating tactile outputs for a user of device 300.

Although some of the examples which follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this way, user inputs (e.g., contacts 460 and 462, and movements thereof) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) are used by the device to manipulate the user interface on the display (e.g., 450 in FIG. 4B) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein.

Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500 includes body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitive display screen 504, hereafter touch screen 504. Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or the touch-sensitive surface) may have one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touch screen 504 (or the touch-sensitive surface) can provide output data that represents the intensity of touches. The user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device 500.

Techniques for detecting and processing touch intensity may be found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, each of which is hereby incorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512 that operatively couples I/O section 514 with one or more computer processors 516 and memory 518. I/O section 514 can be connected to display 504, which can have touch-sensitive component 522 and, optionally, touch-intensity sensitive component 524. In addition, I/O section 514 can be connected with communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. Device 500 can include input mechanisms 506 and/or 508. Input mechanism 506 may be a rotatable input device or a depressible and rotatable input device, for example. Input mechanism 508 may be a button, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personal electronic device 500 can include various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitory computer-readable storage medium, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described above, including processes 800, 900, 1600, 1800, 2100, 2700, 3800, and 4500 (FIGS. 8, 9, 16, 18, 21, 27, 38A-B, and 45, respectively). The computer-executable instructions can also be stored and/or transported within any non-transitory computer-readable storage medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For purposes of this document, a “non-transitory computer-readable storage medium” can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B, but can include other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactive graphical user interface object that may be displayed on the display screen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5 ). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) may each constitute an affordance.

As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4A) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user's intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation) rather than being used to determine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location may be based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm may be applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may be characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.

An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.

In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.

As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.

System Overview

FIG. 6 illustrates an example system 600 for aggregating and sharing wellness data. As mentioned above, wellness data can include, but is not limited to, any type of data associated with a person's health, such as their weight, heart rate, blood pressure, blood glucose level, medication compliance, activity level, or the like. System 600 can be used to collect wellness data associated with a user, store the wellness data, present the wellness data to the user in useful ways, and selectively share the user's wellness data with other users or entities based on permissions set by the user. In addition, in some examples, system 600 can further be used to collect non-wellness data along with wellness data, correlate the non-wellness data with the wellness data, and display the non-wellness data with the wellness data.

System 600 can include one or more user devices 610 including any electronic device, such as a mobile phone, tablet computer, desktop computer, laptop computer, PDA, or the like. In some examples, user device 610 can include a device similar or identical to those shown in FIGS. 1A and 3 and described above. For example, user device 610 can include an operating system and a wellness database 611 for securely storing wellness or non-wellness data along with associated metadata, such as the time the data was recorded, type of data, device used to record the data, user associated with the data, and the like. User device 610 can further include application programming interfaces (APIs) with access controls for storing data in the wellness database 611 and for accessing data stored in the wellness database 611.

User device 610 can be configured to receive wellness or non-wellness data from various sources and can store the received data in the wellness database 611. For example, user device 610 can be configured to receive wellness or non-wellness data from sensors 602, 604, 606, and 608. These sensors can include any type of sensor capable of obtaining wellness data, such as a biometric sensor, activity tracker, or the like. For example, sensors 602, 604, 606, and 608 can include, but are not limited to, a scale, blood pressure cuff, blood glucose monitor, electrocardiogram, step counter, gyroscope, accelerometer, Sp02 sensor, respiration sensor, posture sensor, stress sensor, photoplethysmogram, galvanic skin response sensor, temperature sensor, asthma inhaler, or the like. Sensors 602, 604, 606, and 608 can also include other types of sensors, such as audio sensors, ambient light sensors, electromagnetic sensors, touch sensors, capacitive sensors, and the like, for obtaining non-wellness data, such as situational data, temporal data, personal data, contact data, and the like data. In some examples, each sensor can be a separate device, while, in other examples, any combination of two or more of the sensors can be included within a single device. For example, the gyroscope, accelerometer, photoplethysmogram, galvanic skin response sensor, and temperature sensor can be included within a wearable electronic device, such as a smart watch, while the scale, blood pressure cuff, blood glucose monitor, Sp02 sensor, respiration sensor, posture sensor, stress sensor, and asthma inhaler can each be separate devices. While specific examples are provided, it should be appreciated that other sensors can be used and other combinations of sensors can be combined into a single device.

Sensors 602, 604, 606, and 608 can be used to measure wellness or non-wellness data continuously, intermittently, periodically, or at any other desired frequency or interval of time. For example, sensors 602, 604, 606, and 608 can be used to obtain a single measurement or multiple measurements over a length of time. Sensors 602, 604, 606, and 608 can be configured to measure wellness or non-wellness data at the same intervals of time, or can be configured to measure wellness or non-wellness data at different intervals of time. These intervals may be set by a user or may be a default setting for each sensor. Additionally, sensors 602, 604, 606, 608 can be used to measure wellness or non-wellness data at any time or location desired by the user. Moreover, sensors 602, 604, 606, and 608 can be used with or without the supervision of a healthcare provider. For example, a user can use sensors 602, 604, 606, and 608 to obtain sensor measurements at home without the supervision of a medical professional.

In some examples, user device 610 can include software sensor applications 613 (e.g., third party applications) associated with each of sensors 602, 604, 606, and 608 for interfacing with the sensors to allow user device 610 to receive the wellness or non-wellness data. In these examples, the applications 613 can use the device's APIs to store the wellness or non-wellness data in the wellness database 611 of user device 610. In some examples, the software sensor applications 613 can be Apps and device 610 can be a smart phone, tablet computer, or the like. It should be understood that “third party” can correspond to an entity different than the manufacturer of device 610 and/or the entity that created and/or maintains the operating system of device 610. In these instances, third party applications and their corresponding sensors can communicate and function within the operating system of device 610 according to a predefined device protocol associated with device 610.

The applications 613 can similarly use the device's APIs to access data stored in the wellness database 611. In other examples, user device 610 can be configured to share one or more communication formats with sensors 602, 604, 606, and 608 to allow user device 610 to receive and interpret the wellness or non-wellness data from the sensors. The received data can then be stored in the wellness database 611 of user device 610.

User device 610 can further receive wellness or non-wellness data from its own wellness or non-wellness data sensors 615, such as a GPS sensor, clock, gyroscope, accelerometer, or the like, from a user interacting with user device 610, from another entity, such as a physician, or from other non-sensor sources. For example, using the device's APIs, wellness or non-wellness data can be received from applications 617 on user device 610, such as a clock application, a calendaring application, a gaming application, an application from a healthcare provider, a messaging application, or the like. The wellness or non-wellness data from the applications 617 can originate from a user interacting with the applications, a remote database (e.g., database for a medical website), a healthcare provider institution (e.g., via the institution's App), or the like. In these examples, the usage of the application 617 (e.g., how long you play a video game application, when you play the video game, number of times interacting with a stock application, number of times interacting with a social networking application, length of time interacting with a social networking application, etc.), usage of user device 610 (e.g., length of time on the phone or number of text messages sent as determined from a phone payment application, time spent browsing the Internet as determined from the device's browser, etc.), time spent listening to music as determined from a music or streaming radio application, time spent using a remote application for controlling a television, amount of time or money spent on shopping websites, time spent on pornographic websites (e.g., to identify addictions), weather data from a weather application (e.g., to determine how weather affects a user's health), type of events occurring in the user's life as determined from a calendar (e.g., meetings, birthdays, holidays, etc.), interactions with certain people as determined from a contact list and/or calendar application and/or a messaging application and/or phone of user device 610, or the like, can be received by user device 610 and stored in the wellness database 611.

In some examples, default or user-selected settings can be provided to restrict the access that at least one application (e.g., at least one of applications 613 and 617) on user device 610 has to the wellness database 611 of user device 610 (for both storage and retrieval purposes) and to the sensor data generated by sensors 615 within user device 610 and/or sensor data generated by sensors 602, 604, 606, and 608. For example, an application for tracking a user's running sessions can be granted access to the data generated by the GPS sensor of user device 610, but can be prevented from accessing the user's blood pressure data stored in the wellness database 611. In some examples, an entity other than the owner of user device 610 can set the authorization settings for various applications on user device 610. For example, the manufacturer of user device 610 and/or the entity that created and/or maintains the operating system of user device 610 can evaluate the applications to determine if they should be given access to the user's wellness data and/or sensor data generated or received by user device 610. In some examples, these settings can be overridden by the user.

User device 610 can further include a display for displaying the stored wellness data or non-wellness data. A more detailed description of the interface of the display of user device 610 is described below with respect to FIGS. 10-15, 17, 19-20, 22-26, 28-37, 39-44, 55-62, and 64-66 .

FIG. 7 illustrates system 700 for sharing user wellness data. Referring to FIG. 7 , user server 614 can be communicatively coupled to user device 610 via network 612, which can include the Internet, an intranet, or any other wired or wireless public or private network. User device 610 can be configured to securely transmit the aggregated wellness or non-wellness data and associated metadata stored on the device to user server 614 for storage in user database 616. In some examples, the wellness or non-wellness data and associated metadata can be transmitted to user server 614 for storage in user database 616 in response to an explicit request for such a transfer by the user of device 610, while, in other examples, the wellness or non-wellness data can be synced with the data in user database 616 continuously, periodically, intermittently, or at any desired frequency. In yet other examples, the user's wellness or non-wellness data can be stored only on user device 610 and may not be stored in an external database.

In some examples, user server 614 and user database 616 can be configured to securely store a user's wellness or non-wellness data using a public/private key system that only allows the owner of the wellness or non-wellness data to decrypt the data. Additionally, the wellness or non-wellness data stored in user database 616 can be stored anonymously (e.g., without identifying and/or personal information about the user, such as a legal name, username, time and location data, or the like). In this way, other users, hackers, and the owner/operator of user database 616 cannot determine the identity of the user associated with the data stored in database 616. In some examples, a user can access their wellness or non-wellness data stored in user database 616 from a user device that is different than the one used to upload the wellness or non-wellness data to user server 614. In these instances, the user can be required to provide login credentials to access their wellness or non-wellness data. User server 614 can be configured to perform the authorization process to restrict access to the data within user database 616.

System 700 can further include any number of other user devices 622 and 624 coupled to network 612. In some examples, user devices 622 and 624 can be operated by the same user as user device 610. In these instances, the user can access their wellness or non-wellness data stored in user database 616 by providing user server 614 with the appropriate credentials. In some examples, wellness and non-wellness data can be synced between user database 616 and one or more of user device 610, 622, and 624. In other examples, the user of user devices 622 and 624 can be a person that is different than the user of user device 610. In these examples, the users of devices 622 and 624 cannot access the wellness or non-wellness data of the user of user device 610 without the authorization of the user of user device 610. If authorization is given, wellness or non-wellness data can be shared with the users of user devices 622 and 624. The sharing of this data will be discussed in greater detail below with respect to FIGS. 7-8 .

In some examples, any of the above described sources of wellness or non-wellness data can be configured to measure, generate, or receive wellness or non-wellness data continuously, intermittently, periodically, or at any other desired frequency or interval of time. As such, the wellness or non-wellness data can similarly be stored or updated in wellness database 611 or user database 616 continuously, intermittently, periodically, or at any other desired frequency or interval of time. The frequencies and intervals of time used for measuring, generating, receiving, or storing wellness or non-wellness can be the same or they can be different. Additionally, these frequencies and intervals can be default values or they can be set by a user to provide the user with wellness or non-wellness data that has been updated within a desired length of time.

While not shown, it should be appreciated that many other user devices can be coupled to user server 614 through network 612 to collect and store wellness or non-wellness data for other users in a manner similar to that described above.

User Database

As discussed above, a user's wellness or non-wellness data can be stored in user database 616 and can be shared with other users with the owning user's authorization. The other users can be any type of user, such as a friend, family member, caregiver, physician, social media provider, or the like. Different types and levels of authorization can be granted for the wellness or non-wellness data contained in wellness database 616.

In some examples, the shared wellness or non-wellness data can be pushed to the user device (e.g., user device 622 or 624) of the authorized other user. FIG. 8 illustrates an example process 800 for authorizing and pushing wellness or non-wellness data to authorized other users. At block 802, an identification of an authorized other user can be received. This can be received by a user device (e.g., user device 610) from the user associated with the shared wellness or non-wellness data. The identification can include a username, legal name, contact information, or any other identifier or credential for the other user, along with a level of access, such as access to all of the wellness or non-wellness data or a subset of the wellness or non-wellness data. In some examples, the authorized other user can be grouped into categories of users (e.g., family, friends, other, etc.), where each category is associated with a particular set of wellness data types that those authorized other users are allowed to view. For example, users in the family category can be allowed to view all types of wellness data, while users in the friend category can only view activity data.

At block 804, the user's wellness or non-wellness data can be monitored by the user's device to determine if any updates to the data have been made. If no update has been made, the process can repeat block 804. If, however, an addition or change to the user's wellness or non-wellness data has been identified, the process can proceed to block 806. In some examples, any change to the user's wellness or non-wellness data can cause process 800 to proceed to block 806, while, in other examples, only changes to certain types of the user's wellness or non-wellness data can cause process 800 to proceed to block 806.

At block 806, a notification can be transmitted to one or more authorized other users. For example, a notification can be transmitted from the user's device (e.g., user device 610) to the device of the authorized other user (e.g., user device 622 or 624). The notification can include a message indicating that an update has been made to the user's wellness or non-wellness data. The process can then proceed to block 808.

At block 808, the updated wellness or non-wellness data can be transmitted to the authorized other user. For example, the updated wellness or non-wellness data can be transmitted from the user's device (e.g., user device 610) to the device of the authorized other user (e.g., user device 622 or 624). In some examples, this data can only be transmitted if the authorized other user indicated a desire to view the updated wellness or non-wellness data, while, in other examples, the updated wellness or non-wellness data can be transmitted to the user device of the authorized other user without receiving a request from the authorized other user to view the data.

The pushing of wellness or non-wellness data performed using process 800 can be useful in situations in which a user wants to keep a caregiver or family member (or other user) updated with his/her wellness or non-wellness data. For instance, an elderly parent can grant authorization to push his/her wellness or non-wellness data to a child to allow the child to easily monitor the elderly user's health or medication compliance without having to constantly request this information from the parent.

In other examples, a user's wellness or non-wellness data can be shared with other users by allowing other users to pull the wellness or non-wellness data. FIG. 9 illustrates an example process 900 for authorizing other users to pull wellness or non-wellness data. At block 902, a request to access a particular user's wellness or non-wellness data can be received. The request can identify the user associated with the requested wellness or non-wellness data and, optionally, the portion of the wellness or non-wellness data to be accessed. The identification can include a username, legal name, contact information, or any other identifier or credential for the user. The request can be received by a user device (e.g., user device 610) of the user associated with the requested data from a user device (e.g., user device 622 or 624) of the requesting user.

At block 904, a request for authorization can be transmitted to the user associated with the requested wellness or non-wellness data. In some examples, the request can be transmitted from the user device (e.g., user device 622 or 624) of the requesting user to the user device (e.g., user device 610) of the user associated with the requested data. The request can then be displayed to the user associated with the requested data by the user's device (e.g., user device 610).

At block 906, it can be determined if an authorization has been received from the user associated with the requested wellness or non-wellness data. The authorization can be received in any manner. For example, a prompt can be displayed to the user associated with the requested data on their user device 610. If authorization is denied, the process can return to block 902. If, however, authorization is granted, the process can proceed to block 908.

At block 908, the requested wellness or non-wellness data can be transmitted to the entity that requested access to the wellness or non-wellness data at block 902. The requested wellness or non-wellness data can be transmitted from the user's device (e.g., user device 610) to the requesting entity's device (e.g., user device 622 or 624).

In some examples, if authorization to access a user's wellness or non-wellness data is granted before a request is made at block 902, process 900 can proceed from block 902 to block 908 without performing blocks 904 or 906. For example, if a parent grants access to their wellness or non-wellness data to their child, a request by the child for the parent's wellness or non-wellness data can be received at block 902 and the requested wellness or non-wellness data can be transmitted to the child at block 908 without any intervening action by the parent.

The pulling of wellness or non-wellness data using process 900 can be useful in situations where an authorized other user does not want to be constantly updated with updates to a user's wellness or non-wellness data, but would like occasional access to the data. For example, a physician may want access to a patient's medical records and wellness or non-wellness data just prior to meeting with the patient. In this situation, the physician can request the patient's wellness or non-wellness data and can either receive the requested data or cause a request to be sent to the user device 610 of the patient. In response to receiving an authorization from the patient, the requested data can be sent from user device 610 to the physician's computing device (e.g., user device 622 or 624). In some examples, the received wellness or non-wellness data can be added to an electronic medical record (EMR) associated with the user.

In some examples, whether using a push or pull sharing model, the wellness or non-wellness data of a user may not be permanently stored on the user device of authorized other users. In this way, authorization to these other users can be revoked, causing the user's wellness data to be inaccessible by the formerly authorized other users. Additionally, in some examples, reports detailing or summarizing a user's wellness or non-wellness data can be generated. These reports can then be transmitted via email, secure transfer, or the like, to any desired recipient. In yet other examples, user device 610 can be configured to communicate some or all of the user's wellness or non-wellness data, such as medical insurance information, blood type, medical history, etc., to medical personnel using near field communication or another communication protocol. This can be useful when checking in to a hospital or during medical emergencies when relevant medical data is needed.

Aggregated Data View

As discussed above, user device 610 can be configured to aggregate wellness or non-wellness data associated with a user that was received from the user, from one or more sensors 602, 604, 606, and 608, or from a non-sensor source. User device 610 can also be configured to display the user's aggregated wellness or non-wellness data in various ways using various interfaces.

FIG. 10 illustrates one example interface 1000 that can be used by user device 610 to display a user's aggregated wellness or non-wellness data. Interface 1000 can include any number of partitions 1002, 1004, 1006, 1008, 1010, and 1012, each containing a different type of wellness data associated with the user. In the aggregated view of FIG. 10 , the partitions can be used to display a partial view of a portion of the different types of wellness data. In the examples shown in FIGS. 10-15, 17, and 19-20 , the partitions are illustrated as having the appearance and associated animations of a stack of cards, where each card corresponds to a different partition (and thus, a different type of wellness data). It should be appreciated, however, that the partitions can be displayed in any other desired manner.

Interface 1000 can include a first partition 1002 displayed at the top of the interface that can include an identifier (e.g., name) of the user. As shown, the name “John Smith” of the user of user device 610 is displayed on partition 1002. Interface 1000 can further include button 1001 for viewing wellness data associated with other users. This feature is described in greater detail below with respect to FIGS. 15 and 16 .

Interface 1000 can further include another partition 1004 displayed adjacent to partition 1002 such that it appears to be overlapping partition 1002 like a stacked card. This partition can include an indication of the type of wellness data contained on the partition as well as a partial view (e.g., summary, example, or the like) of a portion the partition's wellness data. Specifically, partition 1004 includes the word “Weight” to indicate that the partition contains weight data associated with the user “John Smith.” Partition 1004 can further include the most recent weight “185 lbs” of “John Smith.”

Interface 1000 can further include another partition 1006 displayed adjacent to partition 1004 such that it appears to be overlapping partition 1004 like a stacked card. This partition can include an indication of the type of wellness data contained on the partition as well as a partial view (e.g., summary, example, or the like) of a portion the partition's wellness data. Specifically, partition 1006 includes the words “Blood Sugar” to indicate that the partition contains blood sugar data associated with the user “John Smith.” Partition 1006 can further include the most recent blood sugar level “164 mg/dL” of “John Smith.”

Interface 1000 can further include another partition 1008 displayed adjacent to partition 1006 such that it appears to be overlapping partition 1006 like a stacked card. This partition can include an indication of the type of wellness data contained on the partition as well as a partial view (e.g., summary, example, or the like) of a portion the partition's wellness data. Specifically, partition 1008 includes the words “Blood Pressure” to indicate that the partition contains blood pressure data associated with the user “John Smith.” Partition 1008 can further include the most recent blood pressure measurement “117/67 mmHg” of “John Smith.”

Interface 1000 can further include another partition 1010 displayed adjacent to partition 1008 such that it appears to be overlapping partition 1008 like a stacked card. This partition can include an indication of the type of wellness data contained on the partition as well as a partial view (e.g., summary, example, or the like) of a portion of the partition's wellness data. Specifically, partition 1010 includes the word “Activity” to indicate that the partition contains activity data (e.g., calories burned) associated with the user “John Smith.” Partition 1010 can further include the current daily number of calories burned “467 kcal” by “John Smith.”

Interface 1000 can further include another partition 1012 displayed adjacent to partition 1010 such that it appears to be overlapping partition 1010 like a stacked card. This partition can include an indication of the type of wellness data contained on the partition as well as a partial view (e.g., summary, example, or the like) of a portion of the partition's wellness data. Specifically, partition 1012 includes the words “Heart Rate” to indicate that the partition contains heart rate data associated with the user “John Smith.” Partition 1012 can further include the most recent heart rate measurement “122 bpm” of “John Smith.” Additionally, since partition 1012 is at the top of the stack of partitions, additional information 1014 and/or options 1016 can be displayed on the face of the partition. In the illustrated example, the additional information includes the minimum, maximum, and resting heart rate of “John Smith” over the span of a week, which was selected using options 1016.

The ordering of some or all of the partitions can be static or dynamic. For example, partition 1002 containing the user's name can remain at the top of the display, while the remaining partitions can be ordered based on the time of day, how recently the wellness data associated with the partition is updated, the frequency that the wellness data associated with the partition is updated, whether a notable event is approaching (e.g., medication that should be taken, a sensor measurement that should be performed, etc.), or the like. The ordering can also be manually changed by the user. If interface 1000 includes more partitions than can be displayed on a single screen, a vertical scrolling can be performed to display the remaining partitions. Alternatively, a 3D scrolling of the partitions may be performed to give the appearance of flipping through a stack of cards.

While specific example partition types have been provided above, it should be appreciated that partitions containing different types of wellness data can be included within interface 1000. Additionally, users can generate customized partitions that can be used to display any desired type of user-entered data. For example, a partition can be created to track the medication compliance of a user. The user can enter the time, amount, and type of medicine taken and this data can be displayed on the created partition. Other custom partitions for different wellness data types, such as nutrition, sleep, smoking, or the like can also be generated.

Additionally, while specific examples of partial views (e.g., summary, example, or the like) of a portion of the partitions' wellness data have been provided above, it should be appreciated that the partial views can summarize or provide examples of the wellness data in different ways. For example, rather than display the most recent value of a particular wellness data type, a mean, mode, median, another single data point, or the like of the wellness data over all or a portion of time (e.g., a week, month, year, etc.) can be displayed on the partitions in the aggregated view. Alternatively, in other examples, a current and average value can be displayed on the partitions in the aggregated view. In yet other examples, the partitions in the aggregated view can include a display of a current value and a goal value for the type of wellness data.

The partitions 1002, 1004, 1006, 1008, 1010, and 1012 can be selected to display an expanded view of the partition containing reconfigured data, additional data, or an enlarged view of the original data contained on the partition. For example, a user can select a partition by tapping on the desired partition displayed on a touch sensitive display, can highlight and click on the partition using a mouse or other input device, or select the desired partition using any other input means. In response to a selection of a partition, user device 610 can hide the contents of the other partitions and display the selected partition on all or most of the display of user device 610.

For example, FIG. 11 illustrates an example interface 1100 that can be displayed in response to a user selecting partition 1004 in interface 1000. In interface 1100, expanded view 1005 of partition 1004 can be displayed prominently within the display of user device 610, while the remaining partitions can be animated as being collapsed off the display into the stack of partitions 1102 displayed at the bottom of the display. In the illustrated example, expanded view 1005 can include additional weight-related data, such as the user's weight, body mass index (BMI), and fat percentage, that were not shown in interface 1000. Expanded view 1005 can further include summaries of the user's weight data, such as a sliding scale 1140 indicating the user's weight relative to a range of weights and a graph 1141 tracking the user's weight throughout the day, week, month, or year. Interface 1100 can further include button 1104 that can cause user device 610 to display options for sharing some or all of their wellness data using any desired communication medium, such as text message, email, social media provider, or the like. In these examples, the wellness data can be encrypted and sent from the user device 610 directly to the user device of the recipient (rather than from user server 614), where the wellness data can be decrypted. To return to the aggregated view of partitions shown in interface 1000, the user can select (e.g., tap, click, or otherwise select) the stack of partitions 1102. It should be appreciated that the contents of interface 1100 and expanded view 1005 are provided as examples, and that expanded view 1005 can instead include any type or summary of weight-related data.

FIG. 12 illustrates an example interface 1200 that can be displayed in response to a user selecting partition 1006 in interface 1000. In interface 1200, expanded view 1007 of partition 1006 can be displayed prominently within the display of user device 610, while the remaining partitions can be animated as being collapsed off the display into the stack of partitions 1102 displayed at the bottom of the display. In the illustrated example, expanded view 1007 can include additional blood sugar-related data, such as the user's blood sugar and units that were not shown in interface 1000. Expanded view 1007 can further include summaries of the user's blood sugar data, such as a sliding scale 1142 indicating the user's blood sugar after a meal relative to a range of typical blood sugar level and a graph 1143 tracking the user's blood sugar throughout the day, week, month, or year. Interface 1200 can also include button 1104, described above. To return to the aggregated view of partitions shown in interface 1000, the user can select (e.g., tap, click, or otherwise select) the stack of partitions 1102. It should be appreciated that the contents of interface 1200 and expanded view 1007 are provided as examples, and that expanded view 1007 can instead include any type or summary of blood sugar-related data.

FIG. 13 illustrates an example interface 1300 that can be displayed in response to a user selecting partition 1008 in interface 1000. In interface 1300, expanded view 1009 of partition 1008 can be displayed prominently within the display of user device 610, while the remaining partitions can be animated as being collapsed off the display into the stack of partitions 1002 displayed at the bottom of the display. In the illustrated example, expanded view 1009 can include additional blood pressure-related data, such as the user's blood pressure and beats per minute (bpm) that were not shown in interface 1000. Expanded view 1009 can further include summaries of the user's blood pressure data, such as a sliding scale 1044 indicating the user's blood pressure relative to typical blood pressure values and a graph 1045 tracking the user's blood pressure throughout the day, week, month, or year. Interface 1300 can also include button 1004, described above. To return to the aggregated view of partitions shown in interface 1000, the user can select (e.g., tap, click, or otherwise select) the stack of partitions 1002. It should be appreciated that the contents of interface 1300 and expanded view 1009 are provided as examples, and that expanded view 1009 can instead include any type or summary of blood pressure-related data.

FIG. 14 illustrates an example interface 1400 that can be displayed in response to a user selecting partition 1010 in interface 1000. In interface 1400, expanded view 1011 of partition 1010 can be displayed prominently within the display of user device 610, while the remaining partitions can be animated as being collapsed off the display into the stack of partitions 1102 displayed at the bottom of the display. In the illustrated example, expanded view 1011 can include additional activity-related data, such as the calories burned, steps taken, and miles traveled by the user that were not shown in interface 1000. Expanded view 1011 can further include summaries of the user's blood pressure data, such as a graph 1146 tracking the intensity of their activity throughout the day, week, month, or year, and summaries 1147 showing the total time spent active, idle, and exercising. Interface 1400 can also include button 1104, described above. To return to the aggregated view of partitions shown in interface 1000, the user can select (e.g., tap, click, or otherwise select) the stack of partitions 1102. It should be appreciated that the contents of interface 1400 and expanded view 1011 are provided as examples, and that expanded view 1011 can instead include any type or summary of activity-related data.

FIG. 15 illustrates an example interface 1500 that can be displayed in response to a user selecting partition 1012 in interface 1000. In interface 1500, expanded view 1013 of partition 1012 can be displayed prominently within the display of user device 610, while the remaining partitions can be animated as being collapsed off the display into the stack of partitions 1102 displayed at the bottom of the display. In the illustrated example, expanded view 1013 can include additional heart rate-related data, such as minimum, maximum, and resting heart rate of the user over a day, week, month, or year. However, unlike partitions 1004, 1006, 1008, and 1010, this data was previously displayed within interface 1000 since partition 1012 was displayed in the aggregated view as being located at the top of the stack of partitions. Expanded view 1013 can further include a summary of the user's heart rate data, such as a graph 1148 tracking the user's heart rate throughout the day, week, month, or year. Interface 1500 can also include button 1104, described above. To return to the aggregated view of partitions shown in interface 1000, the user can select (e.g., tap, click, or otherwise select) the stack of partitions 1102. It should be appreciated that the contents of interface 1500 and expanded view 1013 are provided as examples, and that expanded view 1013 can instead include any type or summary of heart rate-related data.

In some examples, a user's wellness data used to generate the interfaces shown in FIGS. 10-15 and 55 may have been received from one or more sensor devices and/or applications. In these examples, the wellness data of the same type from different devices may be combined and displayed on a single partition. For example, the weight data shown in interface 1100 in FIG. 11 can be obtained from repeated measurements taken using the same scale. Alternatively, some of the measurements could have been obtained from one scale, while the remaining measurements could have been obtained from one or more different scales. As a result, some points in graph 1141 could have been generated using weight data from one scale, while other points in graph 1141 could have been generated using weight data from one or more other scales. In another example, the activity data shown in interface 1400 in FIG. 14 may have been obtained from a single step counting device. Alternatively, the data may be aggregated from a step counting device, a first GPS-enabled watch used to record a user's running session, and a second GPS-enabled watch used to record a user's rowing session. In these examples, graph 1146 showing the intensity of the user's activity can be a segmented graph generated from a combination of the data obtained from the step tracking device and the first and second GPS-enabled watches, with each segment coming from one of the devices. In particular, graph 1146 can include a first segment 1150 generated from data from the step counting device, a second segment 1152 generated from data from the first GPS-enabled watch, and a third segment 1154 generated from data from the second GPS-enabled watch. Aggregating data in this way advantageously allows a user to record and view wellness data in a manner that does not directly tie the wellness data to a particular device or application (e.g., smartphone applications). While three segments are shown in FIG. 14 , it should be appreciated that the segmented graph can include any number of segments corresponding to different sensors and/or applications.

FIG. 16 illustrates an example process 1600 for displaying wellness data according to various examples. At block 1602, an aggregated view of wellness data containing a plurality of partitions similar or identical to partitions 1002, 1004, 1006, 1008, 1010, and 1012 can be displayed on a user device similar or identical to user device 610. The partitions can include an identifier for the type of wellness data displayed on the partition and a partial view (e.g., summary, example, or the like) of a portion of the type of wellness data associated with the partition. For example, an interface similar or identical to interface 1000 can be displayed containing various wellness data partitions 1002, 1004, 1006, 1008, 1010, and 1012.

At block 1604, a selection of one of the displayed partitions can be received. The selection can be received by the user device, and can be in the form of a mouse click, tap on a touch sensitive display, or the like. In response to a selection of the partition, an expanded view of the selected partition can be displayed at block 1606. The expanded view can include a view showing a larger portion of the selected partition and at least one of reconfigured wellness data (e.g., a rearranged view of the wellness data displayed on the selected partition in the aggregated view displayed at block 1602), additional wellness data (e.g., wellness data that was not previously displayed on the selected partition in the aggregated view displayed at block 1602), or an enlarged view of the wellness data displayed in the aggregated view displayed at block 1602 (e.g., a larger view of the same wellness data displayed on the selected partition in the aggregated view displayed at block 1602). Additionally, partitions that were not selected can be reduced in size or removed from the display. For example, any of interfaces 1100, 1200, 1300, 1400, or 1500 can be displayed in response to a selection of partition 1004, 1006, 1008, 1010, or 1012 of interface 1000, respectively.

In some examples, the display presented at block 1606 can include a selectable option (e.g., button 1204) to share wellness data. In other examples, the display presented at block 1606 can further include a selectable option (e.g., partitions 1202) to cause the aggregated view containing partitions displayed at block 1602 to again be displayed. The process can then return to block 1604, where a selection of another partition can be received.

FIG. 17 illustrates an example interface 1700 that can be displayed in response to a user rotating user device 610 to a landscape view. In this orientation, user device 610 can display expanded views of a smaller subset of partitions than displayed in the aggregated view of interface 1000. For example, interface 1700 can include expanded view 1702 of partition 1008, expanded view 1704 of partition 1006, and expanded view 1706 of partition 1012. In the illustrated example, the expanded views of the partitions can include graph representations of the wellness data over various lengths of time. This can allow a user to view the displayed types of wellness data and see how they change relative to each other over time and to evaluate how a change in one type of wellness data relates to a change (or lack thereof) in another type of wellness data. For example, one type of wellness data that can be displayed can include medications taken over time. This data can be compared to a user's blood pressure and heart rate to determine if the medication is having a beneficial or detrimental effect. In some examples, user device 610 can select the types of wellness data to be displayed when user device 610 is rotated into landscape orientation. The selection can be made based on predetermined combinations of wellness data types that are often associated with each other or can be made based on an analysis of the various types of wellness data. In the latter example, wellness data types that are identified as potentially being correlated can be displayed. Wellness data types not shown in the initial display of interface 1700 can be viewed by scrolling through the partitions. Additionally, the partitions can be selected to display more detailed information in the same way as performed in interface 1000.

FIG. 18 illustrates an example process 1800 for displaying wellness data based on an orientation of the device according to various examples. At block 1802, an aggregated view containing a plurality of partitions similar or identical to partitions 1002, 1004, 1006, 1008, 1010, and 1012 can be displayed by a user device similar or identical to user device 610. The partitions can include an identifier for the type of wellness data displayed on the partition and a partial view (e.g., summary, example, or the like) of a portion the type of wellness data associated with the partition. For example, an interface similar or identical to interface 1000 can be displayed containing various wellness data partitions 1002, 1004, 1006, 1008, 1010, and 1012.

At block 1804, a change in orientation of the user device can be detected. For example, a gyroscope and/or an accelerometer within the user device can indicate that the orientation of the device has been changed from portrait to landscape. In response to a detected change in orientation by a threshold amount, the process can proceed to block 1806.

At block 1806, a subset of the plurality of partitions displayed at block 1802 can be selected for display. In some examples, the subset can be a predetermined subset of the plurality of partitions. In other examples, the subset can be selected based on user-defined preferences for display. In yet other examples, the subset of the plurality of partitions can be selected based on an analysis of the wellness data sets associated with each partition to determine if any of the types of wellness data are potentially correlated. If a potential correlation is identified, the partitions associated with the potentially correlated data can be selected at block 1806.

At block 1808, expanded views of the subset of partitions selected at block 1806 can be displayed. In some examples, the identifier for the type of wellness data displayed on the expanded view of the partition and/or the summary, example, or other view of the type of wellness data associated with the partition can be different than that shown on the partitions at block 1802. For example, the summary or example data on each expanded view can be replaced with a graph representation of the wellness data over time, as shown in FIG. 17 . In this way, relationships between the displayed types of wellness data can be observed. In some examples, in response to detecting a change in the orientation of the user device to a portrait orientation, the process can return to block 1802.

As discussed above, in some examples, the user of user device 610 can be granted access to the wellness data of other users. In these examples, user device 610 can allow the user to view the wellness data of other users in a similar format as discussed above with respect to FIGS. 10-18 . For example, as shown by interface 1900 in FIG. 19 , to view the wellness data of other users, the user can laterally scroll the contents of the interface in direction 1906 to cause a first set of partitions 1904 from a first user to be displayed in place of the second set of partitions 1902 from a second user. In particular, the second set of partitions 1902 for the second user can be translated off the display in the direction 1906 of the scroll, while the first plurality of partitions 1904 can be translated onto the display in the same direction 1906 but from the opposite side of the display. It should be appreciated that FIG. 19 illustrates a transitional state in which partitions 1902 are being removed from the display and partitions 1904 are being scrolled in direction 1906 onto the display. As such, only the left side of partitions 1902 and the right side of partitions 1904 are visible. As partitions 1902 and 1904 continue to be scrolled in direction 1906, a smaller portion of partitions 1902 may be visible while a larger portion of partitions 1904 may be visible until partitions 1902 are completely removed from the display and partitions 1904 occupy all or most of the display. While not shown, the top partition of partitions 1904 can include the first user's name and can be displayed as the screen continues to be scrolled in direction 1906. This scrolling operation can be performed any number of times (and in any direction) to scroll through the partitions for all users that the user of device 610 is authorized to access.

FIG. 20 illustrates another example interface 2000 for viewing the wellness data of other users. In some examples, interface 2000 can be displayed in response to a selection of button 1001 of interface 1000. As shown, interface 2000 can include a list of users 2002, 2004, 2006, and 2008 that have authorized the user of user device 610 to access their wellness data. In some examples, the circles next to each user's name can be replaced with an image associated with the user. These images can be the same image as used in device 610's contact list or can include another image. In the illustrated example, users 2002, 2004, 2006, and 2008 have been grouped into different categories (e.g., self, family, and friends). The categories can be used to logically group users together or, as discussed above, can indicate a level of authorization to view the wellness data of the other users. For example, users in the “family” category may have authorized a larger set of their wellness data to be viewed, while users in the “friend” category may have authorized a smaller set of their wellness data to be viewed. In response to a selection of one of users 2002, 2004, 2006, and 2008, partitions 2010 can be updated to reflect the wellness data of the selected user. This can include updating the types of wellness data displayed on the partitions (e.g., based on the types of wellness data the other user has authorized the user of user device 610 to view) as well as the associated partial views (e.g., summary, example, or the like) of portions the wellness data. In other examples, the list of users 2002, 2004, 2006, and 2008 can be displayed in response to vertically scrolling interface 1000 up or down to expose the list of users.

FIG. 21 illustrates an exemplary process 2100 for displaying wellness data associated with two or more users according to various examples. At block 2102, a display of a first plurality of partitions associated with a first user can be displayed. The partitions can be similar or identical to partitions 1002, 1004, 1006, 1008, 1010, and 1012 and can be displayed by a user device similar or identical to user device 610. The partitions can include an identifier for the type of wellness data displayed on the partition and a partial view (e.g., summary, example, or the like) of a portion the type of wellness data associated with the partition. For example, an interface similar or identical to interface 1000 can be displayed containing various wellness data partitions 1002, 1004, 1006, 1008, 1010, and 1012.

At block 2104, a request to view a second plurality of partitions of a second user can be received. The second user can be a user that has authorized the first user to view their wellness data as described above. In some examples, the request can include a user input to scroll the display of the first plurality of partitions displayed at block 2102 and can be received by the user device in the form of rotation of a mouse wheel, an arrow key on a keyboard, a touch and/or swipe on a touch sensitive display, or the like. Similar to the example shown in FIG. 19 , the scroll direction can be in a horizontal direction relative to the contents of the display and can be perpendicular to a scroll direction that causes additional partitions associated with the first user to be displayed. However, it should be appreciated that other scroll directions can be used. In other examples, the request to view the second plurality of partitions can be received in the form of a selection of the second user from a list of users. For example, the second user can be selected from a list of users similar to that shown in FIG. 20 . The list can be displayed in response to a selection of a button (e.g., button 1001) or other selection mechanism, such as vertically scrolling the first plurality of partitions displayed at block 2102 to expose the list of users. In response to receiving the request to view the second plurality of partitions at block 2104, the process can proceed to block 2106.

At block 2106, a display of the second plurality of partitions associated with the second user can be displayed. In some examples, when the request to view the second plurality of partitions received at block 2104 included a request to scroll the display of the first plurality of partitions, the first plurality of partitions can be translated off the display in the direction of the scroll, while the second plurality of partitions can be translated onto the display in the same direction but from the opposite side of the display, as shown in FIG. 19 . In other examples, when the request to view the second plurality of partitions received at block 2104 included a selection of the second user from a list of users, the first plurality of partitions can be replaced with a display of the second plurality of partitions, as shown in FIG. 20 . Additional requests to view wellness data partitions of other users can be received and blocks 2104 and 2106 can be repeated to display some or all of the sets of partitions associated with users that have authorized the user of device 610 to view their wellness data.

It should be appreciated that the processes described above can be combined. For example, process 1800 can be combined with process 1600 such that after the plurality of partitions are displayed at block 1502, a change in orientation of the user device can cause blocks 1804, 1806, and 1808 to be performed. Similarly, process 2100 can be combined with process 1500 such that after the plurality of partitions are displayed at block 1602, the receipt of a request to view partitions associated with other users can cause blocks 2104 and 2106 to be performed to display a plurality of partitions associated with another user.

As mentioned above, systems 600 and 700 can be configured to measure, generate, receive, or store wellness or non-wellness data continuously, intermittently, periodically, or at any other desired frequency or interval of time. Processes 1600, 1800, and 2100 can similarly be performed to update the display of wellness or non-wellness data continuously, intermittently, periodically, or at any other desired frequency or interval of time. For example, the device performing process 1600, 1800, or 2100 can receive updated wellness or non-wellness data from wellness database 611 or user database 616 continuously, intermittently, periodically, or at any other desired frequency or interval of time. In some examples, the device performing process 1600, 1800, or 2100 can receive updates to all wellness or non-wellness data at the same frequency or interval of time. In other examples, the device performing process 1600, 1800, or 2100 can be configured to receive updates to different types of data at different frequencies or intervals of time. For example, heart rate data can be updated every second, while weight data and menstrual flow data can be updated daily. These intervals and frequencies can be default values or can be selected by the user.

Dashboard View

FIG. 22 illustrates one example interface 2200 that can be displayed by user device 610 to display a detailed view of a user's wellness or non-wellness data. Interface 2200 can include any number of partitions 2202, 2204, and 2206, each representing a different type of wellness or non-wellness data associated with the user (e.g., data stored in wellness database 611). In some examples, the partitions can be displayed in a color based on the type of wellness or non-wellness data that it represents. For example, a partition representing nutrition data can be displayed in one color, and a partition representing of fitness data can be displayed in another.

In some examples, a partition can include an identification of the type of wellness or non-wellness data that the partition represents (e.g., calories, steps, weight, or the like), a numerical daily value of the represented type of wellness or non-wellness data, and a graph representation of the represented type of wellness or non-wellness data. For example, partition 2202 can include the text “Calories” to indicate that it represents Calorie data, a current daily value 2210 of 1250 Calories burned, and a graph representation 2208 of the Calorie data over time throughout the day. Similarly, partition 2204 can include the text “Steps” to indicate that it represents step data, a current daily value 2211 of 3100 steps, and a graph representation 2209 of the step data over time throughout the day. Interface 2200 can further include a partial view of partition 2206 showing the text “Weight” to indicate that it represents weight data, as well as a daily value 2212 of 160 lbs. In the illustrated example, the graphs of each partition are non-overlapping with each other.

In some examples, the detailed view of the user's wellness or non-wellness data can include partitions not shown in interface 2200. In these examples, a user can initiate a scroll request by swiping up or down on a touch sensitive display, by clicking and dragging on a display using a mouse or other input device, by manipulating a scroll-wheel, by performing a swiping gesture on a touch pad, or the like. In response to detecting the scroll request, user device 610 can scroll the view of interface 2200 to display other partitions that were not previously displayed (or were partially displayed, such as partition 2206).

For example, FIG. 23 illustrates an example interface 2300 that can be displayed in response to a user initiating a scroll request to scroll the view of interface 2200 in an upward direction. In interface 2300, the remainder of partition 2206 can be displayed to show a graph representation 2214 of the weight data over time throughout the week. Another partition 2216 can also be displayed below partition 2206 in interface 2300. Partition 2316 can include the text “Blood Pressure” to indicate that it represents blood pressure data, a current daily value 2210 of 117/67 mmHg, and a graph representation 2218 of the blood pressure data over time throughout the week. In the example shown in FIG. 23 , graph 2218 includes two vertical bars for each day. The top and bottom of the upper vertical bar for each day can represent the high and low diastolic blood pressure values, respectively, for the day. Similarly, the top and bottom of the lower vertical bar for each day can represent the high and low systolic blood pressure values, respectively, for that day.

In some examples, the order of partitions within interface 2200 or 2300 can be changed in response to detecting a user request to reorder the partitions. In some examples, the request to reorder can include a selecting and holding of one of the partitions for greater than a threshold length of time. After detecting that the threshold length of time has elapsed, user device 610 can animate the partitions in a way that indicates that the partitions can be reordered. In some examples, the partitions can be reordered by dragging a selected partition to a desired location. However, in other examples, the partitions can be reordered in any other desired manner.

While only four partitions 2202, 2204, 2206, and 2216 are shown in the detailed view illustrated by interfaces 2200 and 2300, it should be appreciated that the detailed view can include additional partitions representing any number and any type of wellness or non-wellness data. Similar to partitions 2202, 2204, 2206, and 2216, these additional partitions can include identifications of the type of wellness or non-wellness data that the partitions represent, numerical daily values of the represented types of wellness or non-wellness data, and graph representations of the represented types of wellness or non-wellness data.

In some examples, a graph view of some or all of the wellness or non-wellness data displayed in the detailed view can be displayed in response to a graph-view input. In some examples, the graph-view input can include a detected change in orientation of user device 610. For example, FIG. 24 illustrates an example interface 2400 that can be displayed in response detecting a rotation of user device 610 to a landscape view. The graph view of interface 2400 can include data-set representations 2402, 2404, 2406, and 2408, each representing a different set of wellness or non-wellness data. In the illustrated example, the y-axis of the graph can represent a dependent variable of the various data sets, and the x-axis of the graph can represent an independent variable. For example, if data-set representation 2402 represents a set of Calorie data, then the y-axis dependent variable can be Calories, and the x-axis independent variable can be time. Similarly, if data-set representation 2404 represents step data, then the y-axis dependent variable can be a number of steps, and the x-axis independent variable can be time.

In some examples, the data-set representations can be displayed in a color based on the type of wellness or non-wellness data that it represents. For example, a data-set representation representing nutrition data can be displayed in one color, and a data-set representation of fitness data can be displayed in another. In some examples, the colors used for the different types of wellness or non-wellness data can correspond to the colors used to display the partitions in the detailed views of interfaces 2200 and 2300. For example, a partition representing a set of nutrition data can be displayed in the same color as a data-set representation representing the same set of nutrition data.

In some examples, the independent variable of the x-axis can be the same for all data-set representations shown in the graph view. For example, the time represented by the x-axis can be the same for each data-set representation.

In some examples, the dependent variable of the y-axis can be measured or reported in a different unit for some or all of the data-set representations. For example, the dependent variable for data-set representation 2402 can be expressed in Calories, the dependent variable for data-set representation 2404 can be expressed in a number of steps, the dependent variable for data-set representation 2406 can be expressed in pounds (representing weight data), and the dependent variable for data-set representation 2408 can be expressed in mmHg (representing blood pressure data). Since these data-set representations having different units of measurement can be shown overlaid on the same display, a different vertical y-axis scaling can be used to display the various data-set representations. In some examples, to determine a vertical scale for one of the data-set representations, the minimum and maximum value of the represented data set that are to be displayed within the graph can be determined. For example, to determine the scaling factor for data-set representation 2402 representing Calorie data, the maximum and minimum values of the Calorie data can be determined over the span of time represented by the x-axis of the display. In the example shown in FIG. 24 , this can include determining the maximum and minimum values of the Calorie data over a week. The determined maximum value can be multiplied by a first scaling factor that can have any value (e.g., a value greater than or equal to 1, such as 1.1), and the determined minimum value can be multiplied by a second scaling factor that can be the same or different from the first scaling factor (e.g., a value less than or equal to 1, such as 0.9). The products of the maximum and minimum values multiplied by the first and second scaling factors can be assigned to the maximum vertical position (e.g., highest position on the y-axis) and the minimum vertical position within the graph (e.g., lowest position on the y-axis), respectively. This allows the data-set representation to be fully displayed within the graph. For example, if the maximum and minimum values of the Calorie data represented by data-set representation 2402 is 1000 Calories and 300 Calories, respectively, and if a first scaling factor of 1.1 and a second scaling factor of 0.9 are used, then the maximum vertical position of the y-axis can represent 1100 Calories and the minimum vertical position of the y-axis can represent 270 Calories for data-set representation 2402. This process can be repeated for each of the displayed data-set representations, resulting in a different scale for each of the data-set representations. This advantageously allows the data-set representations to be clearly displayed overlaid on the same graph. For example, if the same scaling factor were instead used for all sets of data, it is possible that the values for one data-set representation can be substantially larger than another, causing the other data-set representation to appear as a flat line.

In some examples, one or more of the displayed data-set representations can be selected to display additional data associated with the selected data-set representation. In some examples, for the purpose of selecting a particular data-set representation by a user, the data-set representations of the graph view shown in interface 2400 can be associated with a range (e.g., a unique range) of vertical positions within the graph. For example, the graph shown in interface 2400 can be divided into four ranges of vertical positions 2410, 2412, 2414, and 2416 separated by the dashed lines. In this example, data-set representation 2402 can be associated with first range of vertical positions 2410, data-set representation 2404 can be associated with second range of vertical positions 2412, data-set representation 2406 can be associated with third range of vertical positions 2414, and data-set representation 2408 can be associated with fourth range of vertical positions 2416.

A selection of one of the data-set representations can be made by entering a user input within a range of vertical positions corresponding to the desired data-set representation, regardless of the horizontal position of the user input. For example, to select data-set representation 2402, a user input in the form of a touch event by a finger or other device on a touch sensitive display, a click of a mouse or other device, a touch event on a touch pad, or the like, can be made at location 2418 having a vertical position located within the first range of vertical positions 2410.

In response to detecting the user input at location 2418 having a vertical position within first range 2410, user device 610 can display an indication that data-set representation 2402 was selected. For example, FIG. 25A shows interface 2500 that can be displayed in response to detecting the input received at location 2418 in interface 2400. As shown, a circle marker can be displayed overlaid on data-set representation 2410 at a horizontal position corresponding to the horizontal position of location 2418. Additionally, a numerical value of 480 kcal can be displayed, indicating that the value of the data set represented by data-set representation 2402 has a value of 480 at the horizontal position of the user input (e.g., horizontal position of location 2418). As shown, data-set representation 2402 can be selected by a user input at location 2418 even though the line of data-set representation 2402 is not located near location 2418. This can advantageously allow a user to select a desired data-set representation without having to select a particular portion of the data-set representation, which can be difficult at locations where multiple data-set representations overlap. In some examples, one of the data-set representations 2402, 2404, 2406, or 2408 can represent blood pressure data. In these examples, for purposes of generating the line of the data-set representation, the dependent variable for the blood pressure data can include an average of the diastolic and the systolic blood pressure. However, the numerical value displayed in response to a selection of the data-set representation for blood pressure data can include a high value for diastolic blood pressure, a low value for diastolic blood pressure, a high value for systolic blood pressure, and a low value for systolic blood pressure associated with the time corresponding to the horizontal position of the user input.

In some examples, one of the data-set representations 2402, 2404, 2406, or 2408 can represent heart rate data. In these examples, the numerical value displayed in response to a selection of the data-set representation for heart rate data can include a high value for heart rate and a low value for heart rate associated with the time corresponding to the horizontal position of the user input.

In some examples, the indication of a selection displayed in response to detecting a user input can further include highlighting an area below the line of the selected data-set representation, as shown in FIG. 25B. For example, the area below the line of the selected data-set representation can be darkened, brightened, displayed with a different color, or otherwise highlighted relative to other portions of the graph to change the line graph into an area graph of the selected data set. In addition, as is the case in FIG. 25B, indicator 2522 can provide a read-out of the value of a dependent variable (e.g., sexual activity events) corresponding to an independent variable corresponding to location 2512. In some examples, the data-set representations that are not currently selected can be removed from the display, greyed out, or otherwise made less visible within the graph.

In some examples, a user input can be continuously applied to the displayed graph and moved in a horizontal direction within one of the range of vertical positions to scrub through values of the selected data-set representation. For example, in response to detecting that the user input received at location 2418 is moved in the left direction, the circle marker displayed over data-set representation 2402 can be animated such that it appears to move along the line of data-set representation 2402 at horizontal positions corresponding to the current horizontal position of the user input. Similarly, the displayed value can change to reflect the value of the data set represented by data-set representation 2402 at the horizontal position of the user input.

In some examples, the vertical ranges of values within the graph associated with the data-set representations can be static. In other examples, the vertical ranges of values within the graph associated with the data-set representations can change. For example, in response to detecting a user input at a location within first range 2410, the size of first range 2410 can expand based on a length of time that the detected user input remains within first range 2410. As a result, the other vertical ranges can contract, or decrease in size. In some examples, the size of first range 2410 can expand to cover the entire graph. In other examples, the size of first range 2410 can expand to a predefined limit. Expanding the size of a selected range of vertical positions advantageously provides the user with a greater tolerance for vertical deviation as the user moves their user input in a horizontal direction to select different portions of a data-set representation.

In some examples, interface 2400 or 2500 can include a compare option 2420 to select the sets of wellness or non-wellness data that are to be displayed within the graph view. For example, FIG. 26 illustrates an example interface 2600 that can be displayed in response to a user selection of compare option 2420 in interface 2400 or 2500. As shown, interface 2600 includes a list of types of wellness or non-wellness data that can be displayed within the graph view. Each type of wellness or non-wellness data can be associated with a selectable option, such as option 2602, to allow the user to add or remove the associated type of wellness or non-wellness data from the graph view. In the illustrated example, the data sets corresponding to Calorie data, step data, blood pressure data, and heart rate data are selected to be displayed within the graph view, while weight data is not. In some examples, the list of wellness or non-wellness data displayed within interface 2600 can include the types of wellness or non-wellness represented by the partitions of interfaces 2200 and 2300.

As another example, FIG. 64A illustrates exemplary user interface 6400 that can be displayed in response detecting a rotation of user device 610 to a landscape view. The graph view of interface 6400 can include data-set representations 6402, 6404, and 6406, each representing a different set of wellness or non-wellness data. In the illustrated example, the y-axis of the graph can represent a dependent variable of the various data sets, and the x-axis of the graph can represent an independent variable. For example, if data-set representation 6402 represents a set of Calorie data, then the y-axis dependent variable can be Calories, and the x-axis independent variable can be time.

Data-set representation 6404, which is shown with discrete dependent variable values, can represent various wellness or non-wellness information. Examples of underlying data represented by data-set representation 6404 are discussed with reference to FIGS. 64B-64F.

Turning to FIG. 64B, data-set representation 6404 can represent the wellness information of basal temperature in some examples. As can be seen, user interface 6410 in user interface 6400 is displayed responsive to touch input 6410 on an indicator of data-set representation 6404 in user interface 6400 (FIG. 64A). User interface 6410 provides basal body temperature range 6424 corresponding to the location of touch input 6410. Range 6424 has a high value as indicated by marker 6426 and a low value as indicated by marker 6428, which are also provided in text read-out 6422.

Turning to FIG. 64C, data-set representation 6404 can represent the wellness information of cervical mucus information in some examples. As can be seen, user interface 6420 is displayed responsive to touch input 6410 on an indicator of data-representation 6404 in user interface 6400 (FIG. 64A). User interface 6420 provides cervical mucus information, which can take on discrete values such as “dry”, “watery,” or “creamy,” for example. As shown, indicator 6414 corresponding to touch input 6410 shows a text read-out 6412 of “creamy”.

Turning to FIG. 64D, data-set representation 6404 can represent the wellness information of menstrual flow in some examples. As can be seen, user interface 6430 is displayed responsive to touch input 6410 on an indicator of data-representation 6404 in user interface 6400 (FIG. 64A). User interface 6420 provides menstrual flow information, which can take on discrete values such as “light,” “medium,” or “heavy,” for example. As shown, indicator 6434 corresponding to touch input 6410 shows a text read-out 6434 of “heavy”.

Turning to FIG. 64E, data-set representation 6404 can represent the wellness information of sexual activity in some examples. As can be seen, user interface 6440 is displayed responsive to touch input 6410 on an indicator of data-representation 6404 in user interface 6400 (FIG. 64A). User interface 6440 provides sexual activity information, such as the number of sexual activity events at a given time interval. As shown, indicator 6444 corresponding to touch input 6410 shows a text read-out 6442 that one sexual activity event has occurred at the time corresponding to the horizontal location of touch input 6410.

Turning to FIG. 64F, data-set representation 6404 can represent the wellness information of menstrual spotting in some examples. As can be seen, user interface 6450 is displayed responsive to touch input 6410 on an indicator of data-representation 6404 in user interface 6400 (FIG. 64A). User interface 6450 provides menstrual spotting information, such as the occurrence of spotting at a given time interval. As shown, indicator 6458 corresponding to touch input 6410 shows a text read-out 6452 indicating menstrual spotting at the time corresponding to the horizontal location of touch input 6410.

As another example, FIG. 65A illustrates exemplary user interface 6500 that can be displayed in response detecting a rotation of user device 610 to a landscape view. The graph view of interface 6500 can include, among others, data-set representations 6506 and 6508 each representing a different set of wellness or non-wellness data. In the illustrated example, the y-axis of the graph can represent a dependent variable of the various data sets, and the x-axis of the graph can represent an independent variable. For example, if data-set representation 6506 represents a set of Calorie data, then the y-axis dependent variable can be Calories, and the x-axis independent variable can be time.

Data-set representation 6508, which is shown as horizontal bar(s), can represent various wellness or non-wellness information. Examples of underlying data represented by data-set representation 6504 are discussed with reference to FIGS. 65B-65C.

Turning to FIG. 65B, data-set representation 6508 can represent the wellness information of cervical mucus information in some examples. As can be seen, user interface 6510 is displayed responsive to touch input 6504 on an indicator of data-representation 6508 in user interface 6500 (FIG. 65A). User interface 6510 provides cervical mucus information, which can take on discrete values such as “dry,” “watery,” or “creamy,” for example. As shown, range 6512 corresponding to touch input 6504 shows a text read-out 6514 of “creamy”. In this example, the dependent variable of data-set representation 6508 takes on values from a set of discrete values (e.g., “dry”, “watery”, and “creamy”). In some examples, range 6512 covers the weekdays corresponding to the location of touch input 6510.

Turning to FIG. 65C, data-set representation 6508 can represent the wellness information of menstrual flow in some examples. As can be seen, user interface 6520 is displayed responsive to touch input 6504 on an indicator of data-representation 6508 in user interface 6500 (FIG. 65A). User interface 6520 provides menstrual flow information, which can take on discrete values such as “light,” “medium,” or “heavy,” for example. As shown, range 6522 corresponding to touch input 6504 shows a text read-out 6524 of “light”. In this example, the dependent variable of data-set representation 6508 takes on values from a set of discrete values (e.g., “light,” “medium,” and “heavy”). In some examples, range 6522 covers the weekdays corresponding to the location of touch input 6510.

As another example, FIG. 66A illustrates exemplary user interface 6600 that can be displayed in response detecting a rotation of user device 610 to a landscape view. The graph view of interface 6600 can include, among others, data-set representations 6602 and 6604 each representing a different set of wellness or non-wellness data. In the illustrated example, the y-axis of the graph can represent a dependent variable of the various data sets, and the x-axis of the graph can represent an independent variable. For example, if data-set representation 6602 represents a set of Calorie data, then the y-axis dependent variable can be Calories, and the x-axis independent variable can be time.

Data-set representation 6604, which is shown as a horizontal bar, can represent wellness or non-wellness information. Examples of underlying data represented by data-set representation 6604 are discussed with reference to FIGS. 66B. As can be seen in FIG. 66B, data-set representation 6604 can represent the wellness information of menstrual spotting in some examples. User interface 6610 provides menstrual spotting information, such as the occurrence of spotting at a given time interval. As shown, range 6612 shows a text read-out 6614 indicating menstrual spotting at the time corresponding to the horizontal location of touch input 6606. In this example, the dependent variable of data-set representation 6604 takes on values from a set of discrete values (e.g., Boolean values of “positive” or “negative”). In some examples, range 6612 covers the weekdays corresponding to the location of touch input 6606.

In some examples, the detailed view of the wellness or non-wellness data can be displayed in response to a detailed-view input received while any of interfaces 2400, 2500, 2510, 6400, 6410, 6420, 6430, 6440, 6500, 6510, 6520, 6600, or 6610 (FIGS. 24, 25, and 64-66 ) are being displayed. In some examples, the detailed-view input can include a detected change in orientation of user device 610. For example, interface 2200, 2300, 5600, 5610, 5620, 5630, 5700, 5710, 5720, 5730, 5800, 5810, 5820, 5830, 5900, 5910, 5920, 5930, 6000, 6010, 6020, 6030, 6100, 6110, 6120, or 6130 (FIGS. 22, 23, and 56-61 ) can be displayed in response to detecting a rotation of user device 610 to a portrait view.

While the graph view shown in interfaces 2400, 2500, 6400, 6500, or 6660 (FIGS. 24, 25, 64, 65, and 66 ) include three or four data-set representations, it should be appreciated that the graph can include any number of data-set representations. Additionally, the number of ranges of vertical positions can change based on the number of displayed data-set representations (e.g., to be equal to the number of displayed data-set representations). For example, if six data-set representations are displayed within the graph, then six discrete ranges of vertical positions can be associated with the data-set representations to allow a user to select the desired data-set representation.

FIG. 27 illustrates an example process 2700 for displaying continuous and/or discrete wellness or non-wellness data according to various examples. Process 2700 can be performed at an electronic device (e.g., device 610) with a display. In some examples, the display can include a touch-sensitive display. In other examples, the display can be separate from a touch-sensitive surface. Some blocks of process 2700 can be combined and/or the order of some blocks can be changed.

As described below, process 2700 provides an intuitive way to select overlapping data-set representations in a graph view. At block 2702, a graph view of wellness or non-wellness data can be displayed on a display of a user device (e.g., user device 610). For example, an interface similar or identical to interface 2400, 2500, 6400, 6500, or 6660 (FIGS. 24, 25, 64, 65, and 66 ) can be displayed. The graph view can include a first data-set representation (e.g., data set representation 2402) of a first data set in which a first dependent variable varies as an independent variable changes and a second data-set representation (e.g., data set representation 2404) of a second data set in which a second dependent variable varies as the independent variable changes.

In some examples, the first data set can include a first set of wellness data, and the second data set can include a second set of wellness data.

In some examples, the first data-set representation can be associated with a first range of vertical positions within the graph (e.g., first range 2410) and the second data-set representation can be associated with a second range of vertical positions within the graph (e.g., second range 2412).

In some examples, the first data-set representation can be displayed in the graph overlapping the second data-set representation. For example, in FIGS. 24 and 25 , data-set representations 2402, 2404, 2406, and 2408 are shown as overlapping in interfaces 2400 and 2500. As another example, FIG. 64 , data-set representations 6402, 6404, and 6406 are shown as overlapping. In some examples, the first data-set representation and the second data-set representation can be colored-coded based on a type of data that they represent.

In some examples, the first range of vertical positions can be uniquely associated with the first data-set representation, and the second range of vertical positions can be uniquely associated with the second data-set representation. For example, first range 2410 is uniquely associated with data-set representation 2402 and second range 2412 is uniquely associated with data-set representation 2404 in interfaces 2400 and 2500.

In some examples, a vertical scale for displaying the first data-set representation can be different from a vertical scale for displaying the second data-set representation. In these examples, displaying the graph can include determining a vertical scale for the first data-set representation based on the maximum and minimum values of the first dependent variable of the first data-set representation that are to be displayed in the graph. Displaying the graph can further include determining a vertical scale for the second data-set representation based on the maximum and minimum values of the second dependent variable of the second data-set representation that are to be displayed in the graph. In some examples, the vertical scale for the first data-set representation can be defined by a maximum vertical position within the graph corresponding to a first multiplying factor multiplied by the maximum value of the first dependent variable of the first data-set representation that are to be displayed in the graph, and a minimum vertical position within the graph corresponding to a second multiplying factor multiplied by the minimum value of the first dependent variable of the first data-set representation that are to be displayed in the graph. In some examples, the vertical scale for the second data-set representation can be defined by a maximum vertical position within the graph corresponding to a third multiplying factor multiplied by the maximum value of the second dependent variable of the second data-set representation that are to be displayed in the graph, and a minimum vertical position within the graph corresponding to a fourth multiplying factor multiplied by the minimum value of the second dependent variable of the second data-set representation that are to be displayed in the graph. In some examples, the dependent variable for the first data set can be measured or reported in different units from the dependent variable for the second data set.

In some examples, the first data set has dependent variables that represent discrete data values, and the second data set has dependent variables that represent values along a continuous range of possible values. As used here, the word “discrete” value refers to distinct, non-continuous values, such as the category values of “heavy,” “medium,” and “light”. A (first) data-set where dependent variables are aligned with discrete elements stands in contrast to a (second) data-set where dependent variables can take on any value along a given range, such as a temperature range, in that dependent variables of the first data set can take on values drawn from a finite set of discrete values, but dependent variables of the second data set can take on an infinite number of value along the applicable range. For example, body temperature can be represented using the discrete values (e.g., categories) of “hot,” “normal,” and “cold,” as well as be represented using data points along a continuous range, such as the value 97.4 degrees along the range of 90 to 110 degrees.

At block 2704, a user input can be detected at a location on the display. Detecting the user input can include detecting a touch or hover event by a finger or other device on a touch sensitive display, a click of a mouse or other device, a touch or hover event on a touch pad, or the like.

At block 2706, a location of the user input can be determined. For example, the vertical and horizontal positions (e.g., y and x-axis coordinates) of the user input can be determined. In some examples, an indication of a selection of the first data-set representation can be displayed, in response to determining that the location of the user input on the display detected at block 2704 has a vertical position associated with the first range of vertical positions. Alternatively, in response to determining that the location of the user input on the display detected at block 2704 has a vertical position associated with the second range of vertical positions, an indication of a selection of the second data-set representation can be displayed. In some examples, an indication of a selection of the first data-set representation can be displayed, in response to determine that the location of the user input on the display detected at block 2704 is located at an indicator representing the value of a discrete dependent variable.

In some examples, displaying the indication of a selection can include displaying a marker overlaid on the selected data-set representation at a horizontal position corresponding to the horizontal position of the location of the user input. For example, a circle marker can be displayed over data-set representation 2402 in interface 2500 of FIG. 25 in response to detecting a user input at location 2418 in interface 2400. In another example, a filled circle marker can be displayed at over an indicator of data-set representation 6404 corresponding to touch input 6410 as shown in FIG. 64D.

In some examples, displaying the indication of a selection can include displaying a numerical and/or textual representation of a data entry of the data set represented by the selected data-set representation. The data entry can be associated with a category value corresponding to the horizontal position of the location of the detected user input. For example, a numerical value of 480 kcal can be displayed in response to receiving a user input at location 2418, as can been seen in FIGS. 24 and 25 . In another example, a textual representation 6434 of “Heavy” can be displayed in response to receiving a user input at location 6410 as shown in FIG. 61D.

In some examples, the first data set or the second data set can include blood pressure data. In these examples, the displayed numerical value of the data entry can include a high value for diastolic blood pressure, a low value for diastolic blood pressure, a high value for systolic blood pressure, and a low value for systolic blood pressure. In some examples, the dependent variable of the first data-set representation or the second data-set representation can include average of blood pressure values.

In other examples, the first data set or the second data set can include heart rate data. In In these examples, the displayed numerical value of the data entry can include a high value for heart rate and a low value for heart rate.

In some examples, the first data set or second data set can include reproductive health data, such as cervical mucus data, basal body temperature, or menstrual flow data. In these examples, the textual representation displayed in response to a selection of the data-set representation for cervical mucus can include “Creamy,” “Dry,” or “Egg white” associated with the time corresponding to the horizontal position of the user input. The textual representation displayed in response to a selection of the data-set representation for basal body temperature can include a temperature reading associated with the time corresponding to the horizontal position of the user input. The textual representation displayed in response to a selection of the data-set representation for menstrual flow can include “Heavy,” “Medium,” or “Light” associated with the time corresponding to the horizontal position of the user input.

In some examples, the first data-set representation can include a first line in the graph. In these examples, displaying the indication that the first data-set representation has been selected can include highlighting an area below the first line. For example, the area below the line of the selected data-set representation can be darkened, brightened, displayed with a different color, or otherwise highlighted relative to other portions of the graph to change the line graph into an area graph of the selected data set. In some examples, the data-set representations that are not currently selected can be removed from the display, greyed out, or otherwise made less visible within the graph.

In some examples, when a given data-set representation is selected, other data-set representations provide an indication that they are not selected, for example, by greying out.

In some examples, the first range of vertical positions within the graph can expand based on a length of time that the user input is detected while a vertical position of the location of the user input is within the first range of vertical positions. In other examples, the second range of vertical positions within the graph can expand based on a length of time that the user input is detected while the vertical position of the location of the user input is within the second range of vertical positions.

At block 2708, a detailed-view input can be detected at the electronic device. In some examples, detecting the detailed-view input can include detecting a change in orientation of the electronic device while displaying the graph. For example, detecting the detailed-view input can include detecting a change in orientation of the electronic device from a landscape view (e.g., shown in FIGS. 24-26 ) to a portrait view (e.g., shown in FIGS. 22-23 ). In other examples, the detailed-view input can include other types of inputs.

At block 2710, in response to detecting the detailed-view input, a detailed view of the first data set and the second data set can be displayed. For example, a detailed view similar or identical to those shown in interfaces 2200 and 2300 can be displayed. The detailed view can include a first partition associated with the first data set (e.g., partition 2202) and a second partition associated with the second data set (e.g., partition 2204).

In some examples, the first partition can include a first graph representation of the first data set (e.g., graph 2208), and the second partition can include a second graph representation of the second data set (e.g., graph 2210). In some examples, unlike the first and second data-set representation of the graph view, the first graph representation can be non-overlapping with the second graph representation in the detailed view.

In some examples, the first partition can be displayed in a color matching a color of the first data-set representation, and the second partition can be displayed in a color matching a color of the second data-set representation. For example, partition 2202 can be displayed in a color matching a color of data-set representation 2402, and partition 2204 can be displayed in a color matching a color of data-set representation 2404.

In some examples, process 2700 can further include detecting a request to scroll the detailed view and, in response to detecting the request to scroll the detailed view, scrolling the detailed view. For example, the detailed view shown in interface 2200 can be scrolled in the upward direction to display interface 2300 containing other partitions that were not previously displayed.

In some examples, process 2700 can further include detecting a request to reorder the first partition and the second partition and, in response to detecting the request to reorder the first partition and the second partition, reordering the first partition and the second partition within the detailed view. In some examples, detecting the request to reorder can include detecting a selection of one of the partitions for greater than a threshold length of time. After detecting the selection for the threshold length of time, user device 610 can animate the partitions in a way that indicates that the partitions can be reordered. The partitions can be displayed reordered in response to detecting that a selected partition is dragged to a new location within the detailed view.

In some examples, process 2700 can further include detecting a graph-view input at the electronic device and, in response to detecting the graph-view input, displaying the graph comprising the first data-set representation of the first data set and the second data-set representation of the second data set. In some examples, detecting the graph-view input can include detecting a change in orientation of the electronic device. For example, interface 2400 can be displayed in response to detecting a change in orientation of the electronic device from a portrait view to a landscape view.

It should be understood that the particular order in which the operations in FIG. 27 have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other processes described herein (e.g., processes 900, 1600, 1800, 2100, 2700, 3800, or 4500) are also applicable in an analogous manner to process 2700 described above with respect to FIG. 27 . For brevity, these details are not repeated here.

Input and Output of Heath Data with Granularity

FIG. 28 illustrates one example interface 2800 that can be displayed by user device 610 to display a user's wellness or non-wellness data. Interface 2800 can include a list 2802 of categories of wellness or non-wellness data. The categories can include one or more sub-categories of wellness or non-wellness data. The sub-categories can further include any number of additional sub-categories. For example, the category “Fitness” can include sub-categories “Body Mass Index,” “Body Fat Percentage,” “Height,” “Body Mass,” “Lean Body Mass,” “Steps,” “Distance,” “Calories Burned,” “Active Hours,” and “Flights of Stairs.” The category “Vital Signs” can include sub-categories “Heart Rate,” “Systolic Blood Pressure,” “Diastolic Blood Pressure,” “Oxygen Saturation,” “Respiratory Rate,” and “Body Temperature.” The category “Lab Results” can include sub-categories “Blood Glucose” and “Blood Alcohol Content.” The category “Nutrition” can include sub-categories “Total Fat,” “Polyunsaturated Fat,” “Monounsaturated Fat,” “Saturated Fat,” “Cholesterol,” “Sodium,” “Potassium,” “Carbohydrates from Sugar,” “Dietary Fiber,” “Sugars,” “Dietary Calories,” “Calories from Fat,” “Protein,” “Vitamin A,” “Vitamin B6,” “Vitamin B12,” “Vitamin C,” “Vitamin D,” “Vitamin E,” “Vitamin K,” “Calcium,” “Iron,” “Thiamin,” “Riboflavin,” “Niacin,” “Folic Acid,” “Biotin,” “Pantothenic Acid,” “Phosphorus,” “Iodine,” “Magnesium,” “Zinc,” “Selenium,” “Copper,” “Manganese,” “Chromium,” “Molybdenum,” and “Chloride.” The category “Diagnostics” can include sub-categories “Number of Time Fallen,” “Galvanic Skin Response,” and “Body Heat Flux.” The category “Medications” can include sub-category “Inhaler Use.” The category “Sleep” can include subcategories “Hours Slept.” The category “Me” can include sub-categories “Name,” “Birthdate,” “Gender,” “Blood Type.” It should be appreciated that the lists above are provided only as examples, and that additional or fewer categories can be included within interface 2800. Additionally, it should be appreciated that the categories of interface 2800 can include additional or fewer sub-categories.

In some examples, each item in list 2802 can include an indicator 2804 that can be color-coded based on the type of wellness or non-wellness data of the associated item in list 2802. For example, the indicator 2804 associated with “Fitness” can have a different color than the indicator 2804 associated with “Vital Signs.” In some examples, the items in list 2802 can further include a selectable option 2806 that can be used to expand the associated category.

For example, FIG. 29 illustrates interface 2900 that can be displayed in response to a selection of option 2806 associated with “Fitness.” As shown, interface 2900 can include a list 2902 of sub-categories that fall under the broader category of “Fitness” that was selected in interface 2800. The list 2902 of sub-categories can be displayed in place of the previously displayed list 2802. Similar to list 2802, the items in list 2902 can include an indicator 2904 that can be color-cored based on the type of wellness or non-wellness data of the associated item in list 2902. In this example, since all of the sub-categories displayed within list 2902 fall under the same category or type of wellness or non-wellness data, the indicators 2904 associated with each item can be the same color. In some examples, the color of indicators 2904 associated with the items in list 2902 can be the same color as indicator 2804 associated with “Fitness.” In other examples, the color of indicators 2904 associated with the items in list 2902 can be a different shade of the color of indicator 2804 associated with “Fitness.” For example, indicators 2904 can be light green, while indicator 2804 associated with “Fitness” can be dark green.

Referring back to FIG. 28 , interface 2800 (and interface 2900) can further include search box 2808 for performing keyword searches within the categories listed in list 2802. For example, FIG. 30 illustrates interface 3000 that can be displayed in response to a user entering the search query “Calories” in search box 2808. As shown, interface 3000 can include a list 3002 of sub-categories that match the search query “Calories.” The sub-categories can be sub-categories of any of the categories of list 2802. For “Calories Burned” can be a sub-category of “Fitness,” “Dietary Calories” can be a sub-category of “Nutrition,” and “Calories From Fat” can be a sub-category of “Nutrition.” Interface 3000 can further include indicators 3004 associated with the items in list 3002. Similar to indicators 2804 and 2904, indicators 3004 can be color-coded based on the type of wellness or non-wellness data of the associated item in list 3002. In this example, indicator 3004 of “Dietary Calories” can be the same color as indicator 3004 of “Calories From Fat” since they both fall within the broader category of “Nutrition.” In some examples, the color of indicators 3004 of “Dietary Calories” and “Calories From Fat” can be the same color as indicator 2804 for “Nutrition.” In other examples, the color of indicators 3004 of “Dietary Calories” and “Calories From Fat” can be a different shade of the color of indicator 2804 for “Nutrition.” The indicator 3004 for “Calories Burned” can be a different color from indicators 3004 of “Dietary Calories” and “Calories From Fat” since “Calories Burned” falls within a different category (e.g., “Fitness”). In some examples, the color of indicator 3004 of “Calories Burned” can be the same color as indicator 2804 for “Fitness.” In other examples, the color of indicator 3004 of “Calories Burned” can be a different shade of the color of indicator 2804 for “Fitness.”

In some examples, any of the sub-categories shown in interfaces 2900 and 3000 can be selected to display a detailed view of the sub-category. For example, FIG. 31 illustrates an example interface 3100 that can be displayed in response to a selection of “Calories Burned” from either interface 2900 or 3000. As shown, interface 3100 can include a text indication of the type of wellness or non-wellness data being displayed in the detailed view. For example, interface 3100 include the text “Calories Burned” to indicate that the information displayed within interface 3100 represents information associated with Calories burned.

In some examples, interface 3100 can further include a current daily value 3104 of 1250 kcal and a graph representation 3102 showing the number of Calories burned over time throughout the day. Interface 3100 can further include “Show All Data” option 3106 that can be used to display all data that falls within the sub-category of “Calories Burned.” For example, FIG. 33 illustrates an example interface 3300 that can be displayed in response to a selection of option 3106 in interface 3100. As shown, interface 3300 can include a list 3302 of all data entries that represent calories burned (e.g., stored in wellness database 611). As shown, the data entries in list 3302 can include a numerical value of the data entry and an associated date (and can also include a time) that the corresponding data entry was recorded. For example, the first data entry in list 3302 can include the number 860 associated with date Mar. 1, 2014, indicating that 860 Calories were burned on Mar. 1, 2014. The data entries in list 3302 can further include an indicator 3304. Indicator 3304 can include a graphic, text, or other image that represents the source of the data entry. For example, if the first data entry was obtained from a wearable electronic Device 1, indicator 3304 associated with that data entry can include an image of the logo of the company that manufactured Device 1 or some other image associated with Device 1. Similarly, if the second data entry in list 3302 was obtained from a software application App 1, indicator 3304 associated with the second data entry can include an image associated with a logo of the company that created App 1 or some other image associated with App 1.

While shown for Calories burned, it should be appreciated that a list of data entries associated with any type of sub-category of wellness or non-wellness data can be displayed in a similar manner.

Referring back to FIG. 31 , interface 3100 can further include “Add Data Point” option 3108 that can be used to display an interface for manually entering a data entry within the sub-category of “Calories Burned.” For example, FIG. 34 illustrates an example interface 3400 that can be displayed in response to a selection of option 3108 in interface 3100. As shown, interface 3400 can include fields 3402, 3404, and 3406 for entering the date, time, and number of Calories burned, respectively, for the data entry being input. Interface 3400 can further include numerical input pad 3408 for populating fields 3402, 3404, and 3406. Interface 3400 can further include “Add” button 3410 that can be selected to add the information contained in interface 3400 as a data entry within the Calories burned sub-category (e.g., to be stored in wellness database 611). Interface 3400 can further include “Cancel” button 3412 for canceling entry of the data entry.

Referring back to FIG. 31 , interface 3100 (and interface 3200) can further include “Show On Dashboard” option 3112 having option 3120 for selectively causing the associated sub-category of data (e.g., Calories Burned) to be displayed in the detailed view of interfaces 2200 and 2300. When the switch of option 3120 is placed in the on position, the associated sub-category of data can be included within the detailed view of interfaces 2200 and 2300. However, when the switch of option 3120 is placed in the off position, the associated sub-category of data may not be included within the detailed view of interfaces 2200 and 2300.

As shown in FIG. 31 , interface 3100 can further include graphic 3114. Graphic 3114 can include any image or other graphical representation of the wellness or non-wellness data represented displayed in interface 3100. For example, graphic 3114 can include a balance showing the relative values of Calories consumed and Calories expended by the user. However, it should be appreciated that any other graphic or image can be shown.

In some examples, the detailed view of the sub-category can further include additional information not shown in interface 3100. In these examples, a user can initiate a scroll request by swiping up or down on a touch sensitive display, by clicking and dragging on a display using a mouse or other input device, by manipulating a scroll-wheel, by performing a swiping gesture on a touch pad, or the like. In response to detecting the scroll request, user device 610 can scroll the view of interface 3100 to display information that was not previously displayed (or was partially displayed).

For example, FIG. 32 illustrates an example interface 3200 that can be displayed in response to a user initiating a scroll request to scroll the view of interface 3100 in an upward direction. In interface 3200, graphic 3114 and options 3106, 3108, 3110, and 3112 can still be displayed, but can be located closer to the top of the display. Interface 3200 can further include text description 3122 below graphic 3114. Text description 3122 can include a text describing what the wellness or non-wellness data shown in interface 3200 represents. For example, text description 3122 can provide an explanation about what “Calories Burned” represents, such as how it is calculated, what an average daily value is for a typical person, how to increase the amount of Calories burned, or the like.

Referring back to FIG. 31 , interface 3100 can further include “Share Data” option 3110 having option 3116 for turning data sharing on or off. Data sharing can represent the ability for other devices or applications to access a user's wellness or non-wellness data (e.g., stored in wellness database 611). For example, FIG. 35 illustrates an example interface 3500 that can be displayed in response to a selection of option 3110 in interface 3100. As shown, interface 3500 can include share option 3502 having selectable option 3512. The position of the switch of option 3512 can be used to turn data sharing on or off. For example, when moved to the right, as shown in FIG. 35 , the switch of option 3512 can turn on sharing option 3502. However, when moved to the left, the switch of option 3512 can turn off sharing option 3502.

Interface 3500 can further include a list 3504 of known possible destinations of wellness or non-wellness data. This list can include known devices or software applications that can potentially receive a user's wellness or non-wellness data (e.g., stored in wellness database 611). When option 3512 of share option 3502 is moved to the off position, data sharing for all listed devices and applications can be turned off. As such, selectable options 3514, 3516, and 3518 can be removed from interface 3500 or otherwise made inactive. When option 3512 of share option 3502 is moved to the on position, selectable options 3514, 3516, and 3518 associated with the destinations in list 3504 can be displayed or made selectable. Similar to option 3512, the position of the switches of options 3514, 3516, and 3518 can be changed to turn data sharing on or off for the associated destination. For example, option 3514 for Device 1 is in the off position, indicating that data sharing is not turned on for Device 1. Options 3516 and 3518, however, are in the on position, indicating that data sharing is turned on for App 1 and App 2. When data sharing is turned on, the associated device or application can access the user's wellness or non-wellness data (e.g., stored in wellness database 611). For example, App 1, which can represent a weight tracking application, can access a user's fitness and nutrition data to track the user's caloric intake and outtake. When data sharing is turned off, the associated device or application may be prevented from accessing the user's wellness or non-wellness data (e.g., stored in wellness database 611). For example, Device 1 may be unable to access data stored in wellness database 611.

Interface 3500 can further include source list 3506 containing a list of known devices and applications that can potentially provide wellness or non-wellness data (e.g., to be stored in wellness database 611). The devices and applications in source list 3506 can be arranged in an order based on their priority. For example, as shown, Device 1 has priority over Device 2, which has priority over App 3. These relative priorities can be used to de-duplicate wellness or non-wellness data generated by two or more of the sources. For example, if Device 1 represents a fitness-tracking watch, and Device 2 represents a mobile phone, it is possible that both devices can provide step data associated with the user. Thus, by prioritizing the different sources, data from a higher ranked source can be used in place of data from a lower ranked source, or otherwise prioritized over data from the lower ranked source. This can be advantageous when one device is more likely to produce more accurate results than another. In some examples, duplicate data entries can be detected by identifying two or more data entries having metadata indicating that they are of the same type (e.g., step data, Calories burned, etc.) and having an associated timestamp that is within a threshold length of time from each other.

In some examples, interface 3500 can further include edit option 3508 for changing the order of the sources of source list 3506. For example, in response to a selection of option 3508, each item in source list 3506 can be moved (e.g., by clicking and dragging, etc.) relative to each other. The new order of sources within source list 3506 can define a new prioritization between sources.

In some examples, the “Sources” option of source list 3506 can be selected to display a more detailed view of the sources. For example, FIG. 36 illustrates an example interface 3600 that can be displayed in response to a selection of the “Sources” option of source list 3506. As shown, interface 3600 can include a source list 3606 similar to source list 3506. However, source list 3606 can further include sources App 2 and App 1, which were not displayed within interface 3500 because they were unable to be fit within the display. Interface 3600 can further include a numerical indicator associated with a source (e.g., Device 1) that indicates a number of new types of wellness or non-wellness data that the associated source can provide. For example, since the last time the user viewed interface 3600, Device 1 is now able to provide two new types of data (e.g., Calories burned and flights of stairs climbed). Interface 3600 can further include option 3610 associated with the sources in source list 3606 to provide more detailed control over the types of data that each source can provide.

For example, FIG. 37 illustrates an example interface 3700 that can be displayed in response to a selection of option 3610 in interface 3600 or option 3510 in interface 3500 associated with Device 1. As shown, interface 3700 can include upload option 3702 having selectable option 3704. The position of the switch of option 3704 can be used to turn data uploading from the device or application on or off (e.g., to be stored in wellness data base 611). For example, when moved to the right, as shown in FIG. 37 , the switch of option 3704 can turn on data uploading by Device 1. However, when moved to the left, the switch of option 3704 can turn off data uploading by Device 1.

Interface 3700 can further include a list 3706 of data types that can be provided by Device 1. When option 3512 of share option 3704 is moved in the off position, data uploading for all listed types of data can be turned off. As such, selectable options 3708, 3710, 3712, and 3714 can be removed from interface 3700 or otherwise made inactive. When option 3704 of upload data option 3702 is moved to the on position, selectable options 3708, 3710, 3712, and 3714 associated with the list 3706 of data types can be displayed or made selectable. Similar to option 3704, the position of the switches of options 3708, 3710, 3712, and 3714 can be changed to turn data uploading on or off for the associated types of data. For example, option 3708 for Blood Pressure is in the off position, indicating that data uploading is not turned on for Blood Pressure data from Device 1. Options 3710, 3712, and 3714, however, are in the on position, indicating that data uploading is turned on for Calorie, Step, and Stairs Climbed data. When data uploading is turned on, the associated type of data can be provided by the device or application to be stored by user device 610 (e.g., in wellness database 611). For example, Calorie data generated by Device 1 can be received by user device 610 from Device 1 and stored in wellness database 611. When data uploading is turned off, the associated type of data may not be provided by the device or application to be stored by user device 610 (e.g., in wellness database 611). For example, blood pressure data generated by Device 1 may not be received by user device 610 from Device 1 and stored in wellness database 611. The options of interface 3700 advantageously allow a user to specifically define what types of data can be provided by a particular device or application.

While the examples shown in FIGS. 30-34 were for Calories burned, it should be appreciated that similar interfaces can also be displayed for other types of wellness or non-wellness data.

FIGS. 55A-55B illustrate other exemplary interfaces that can be displayed by user device 610 to display a user's wellness or non-wellness data. As seen in FIG. 55A, interface 5500 can include Selection Box 5502 that allows a user to select whether to view the data in a list view or calendar view. When the list view is selected, as depicted in FIG. 55 , interface 5500 shows a list 5504 of categories of wellness or non-wellness data. Responsive to selection of option 5506 (reproductive health), device 610 displays interface 5510 which shows the sub-categories of wellness information associated with option 5506. These sub-categories of wellness information is described with respect to FIGS. 56-61 .

Turning to FIGS. 56A-56D, responsive to selection of option 5508 (FIG. 55B), one of interfaces 5600, 5610, 5620, or 5630 (FIGS. 56A-56D) is displayed, in some examples. As can be seen in FIG. 56A, interface 5600 depicts basal body temperature information at the hourly level of detail for a given day. Interface 5600 includes temperature label 5608, and indicator 5606 indicating temperature (e.g., dependent variable) for a given time (e.g., independent variable). Turning to FIG. 56B, interface 5610 depicts basal body temperature information at the daily level of detail for a given week. Notably, indicator 5611 depicts the high basal body temperature for a given day, indicator 5612 depicts the low basal body temperature for a given day, and range 5614 depicts the range of basal body temperatures for a given day. In addition, category label 5616 takes on the lowest basal body temperature for the week, while category label 5618 takes on the highest basal body temperature for the week. Similarly, interface 5620 depicted in FIG. 56C depicts basal body temperatures for a given month, and interface 5630 depicted in FIG. 56D depicts basal body temperatures for a given year. In some embodiments, a user navigates between user interfaces 5600, 5610, 5620, and 5630 (FIGS. 56A-56D) by pinching or de-pinching touch input on device 610.

Turning to FIGS. 57A-57D, responsive to selection of option 5510 (FIG. 55B), one of interfaces 5700, 5710, 5720, or 5730 (FIGS. 57A-57D) is displayed, in some examples. As can be seen in FIG. 57A, interface 5700 depicts cervical mucus information at the hourly level of detail for a given day. Interface 5700 includes indicator 5706 whose horizontal position corresponds to an independent variable (e.g. time of day) of the data set, and whose vertical position corresponds to a dependent variable (e.g., mucus consistency) of the data set. Turning to FIG. 57B, interface 5710 depicts cervical mucus information at the daily level of detail for a given week. Notably, range indicator 5716 depicts the median consistency of cervical mucus for a period during which cervical mucus is observed. Similarly, interface 5720 depicted of FIG. 57C depicts median cervical mucus consistency across different periods 5726 and 5728 during which cervical discharge is observed, across the timeframe of a month. Similarly, interface 5730 depicted of FIG. 57D depicts median cervical mucus consistency across different periods 5736 and 5738 during which cervical discharge is observed, across the timeframe of a year. In some embodiments, a user navigates between user interfaces 5700, 5710, 5720, and 5730 (FIGS. 57A-57D) by pinching or de-pinching to zoom touch input on device 610.

Turning to FIGS. 58A-58D, responsive to selection of option 5512 (FIG. 55B), one of interfaces 5800, 5810, 5820, or 5830 (FIGS. 58A-58D) is displayed, in some examples. As can be seen in FIG. 58A, interface 5800 depicts menstrual flow information at the hourly level of detail for a given day. Interface 5800 includes indicator 5806 whose horizontal position corresponds to an independent variable (e.g. time of day) of the data set, and whose vertical position corresponds to a dependent variable (e.g., menstrual flow) of the data set. Turning to FIG. 58B, interface 5810 depicts menstrual flow information at the daily level of detail for a given week. Notably, indicator 5818 marks the beginning of a period of menstrual flow as indicated by range 5816. Similarly, interface 5820 of FIG. 58C depicts menstrual flow for a month, with indicator 5828 marking the beginning of a period of menstrual flow as indicated by range 5826. Similarly, interface 5830 of FIG. 58D depicts menstrual flow for a year. Exemplary range indicators include 5836 and 5838. Exemplary beginning-of-cycle indicators include 5837 and 5839. In some embodiments, a user navigates between user interfaces 5800, 5810, 5820, and 5830 (FIGS. 58A-58D) by pinching or de-pinching to zoom touch input on device 610.

Turning to FIGS. 59A-59D, responsive to selection of option 5514 (FIG. 55B), one of interfaces 5900, 5910, 5920, or 5930 (FIGS. 59A-59D) is displayed, in some examples. As can be seen in FIG. 59A, interface 5900 depicts ovulation information at the hourly level of detail for a given day. Interface 5900 includes indicators 5906 whose horizontal positions correspond to independent variables (e.g. times of day) of the data set, and whose vertical positions correspond to dependent variables (e.g., ovulation levels) of the data set. Turning to FIG. 59B, interface 5910 depicts ovulation information at the daily level of detail for a given week. Notably, indicator 5918 marks the end of a period of ovulation as indicated by range 5916. Similarly, interface 5920 depicted of FIG. 59C depicts ovulation information for a month, while interface 5930 (FIG. 59D) depicts ovulation information for a year. In interface 5920, the end of range indicator 5926 is marked by indicator 5926 to indicate the end of an ovulation cycle. In interface 5930, range indicator 5936 includes indicator 5937 indicating positive ovulation and end-of-ovulation indicator 5938 indicating the end of an ovulation cycle. In some embodiments, a user navigates between user interfaces 5900, 5910, 5920, and 5930 (FIGS. 59A-59D) by pinching or de-pinching to zoom touch input on device 610.

Turning to FIGS. 60A-60D, responsive to selection of option 5516 (FIG. 55B), one of interfaces 6000, 6010, 6020, or 6030 (FIGS. 60A-60D) is displayed, in some examples. As can be seen in FIG. 60A, interface 6000 depicts sexual activity information at the hourly level of detail for a given day. Category label 6006 is provided to indicate that the vertical location of indicator 6008 corresponds to one sexual activity event. Turning to FIG. 60B, interface 6010 depicts sexual activity information at the daily level of detail for a given week, with indicators 6016 and 6018 showing activity levels for different days of the week. Similarly, interface 6020 depicted of FIG. 60C depicts sexual activity information for a month, while interface 6030 (FIG. 60D) depicts sexual activity information at the monthly level of detail for a year. For example, indicator 6038 in interface 6030 indicates five sexual events have occurred in December 2014. In some embodiments, a user navigates between user interfaces 6000, 6010, 6020, and 6030 (FIGS. 60A-60D) by pinching or de-pinching to zoom touch input on device 610.

Turning to FIGS. 61A-61D, responsive to selection of option 5518 (FIG. 55B), one of interfaces 6100, 6110, 6120, or 6130 (FIGS. 61A-61D) is displayed, in some examples. As can be seen in FIG. 61A, interface 6100 depicts menstrual spotting information at the hourly level of detail for a given day. Interface 6100 includes indicators 6106 whose horizontal positions correspond to independent variables (e.g. times of day) of the data set, and whose vertical positions correspond to dependent variables (e.g., positive or no spotting) of the data set. Turning to FIG. 61B, interface 6110 depicts menstrual spotting information at the daily level of detail for a given week, with range indicator 6116 showing that spotting has occurred on multiple days of the week. Similarly, interface 6120 depicted of FIG. 61C depicts spotting information for a month, while interface 6130 (FIG. 61D) depicts menstrual spotting information at for a year. In some embodiments, a user navigates between user interfaces 6100, 6110, 6120, and 6130 (FIGS. 61A-61D) by pinching or de-pinching to zoom touch input on device 610.

As previously described with respect to FIG. 28 , a category of wellness or non-wellness data can include one or more sub-categories. For example, the category “Reproductive Health” can include sub-categories “Menstrual Flow,” “Cervical Mucus,” “Basal Temperature,” “Sexual Activity,” “Ovulation,” and so forth. The category “Lab Results” can include sub-categories “Blood Glucose” and “Blood Alcohol Content.” It should be appreciated that list 5504 is provided only as an example, and that additional or fewer categories can be included within interface 5500. Additionally, it should be appreciated that the categories of interface 5500 can include additional or fewer sub-categories.

FIGS. 62A and 62B illustrate another example interface 6200 that can be displayed by user device 610 to display a user's wellness or non-wellness data. In this example, the calendar view in Selection Box 6202 is selected, rather than the list view as depicted in FIGS. 55A and 55B. When the calendar view is selected, interface 6200 displays calendar 6208 with a selected day 6210. Interface 6200 can include wellness or non-wellness data associated with the selected day 6210. For example, interface 6200 can include wellness or non-wellness data for a list 6204 of wellness or non-wellness categories, such as “Reproductive Health” category 6202. List 6204 also includes sub-categories, along with the value 6212 of applicable sub-categories for the selected day 5710. List 6204 of sub-categories is associated with the list 5504 of categories depicted in the list view of FIG. 55A. For example, list 6204 lists sub-categories such as menstrual flow, cervical mucus, and basal temperature as being associated with the category 6206 of “Reproductive Health.”

In some examples, the list of sub-categories can be scrolled to display sub-categories associated with additional categories. For example, as depicted in FIG. 62B, scrolling list 6204 reveals sub-categories associated with the “Lab Results” category. In some examples, the categories (and associated sub-categories) are displayed in interfaces 6200 and 6210 in the order in which they appear in the list view of interface 5500; e.g., in the order of list 5504 (FIGS. 55A and 55B). Thus, in this example, scrolling list 6204 causes the sub-categories associated with the “Lab Results” category 6216 to appear after the sub-categories associated with the “Reproductive Health” category as this is the order in which these categories appear in list 5504 (FIGS. 55A and 55B).

FIG. 63 illustrates an example interface 6300 for entering discrete wellness or non-wellness data, in this example menstruation sample information. Interface 6300 allows a user to enter a category value for the “Menstrual Flow” sub-category of the “Reproductive Health” category. Interface 6300 includes selection box 6302 to allow a user to select a data type corresponding to a category or sub-category. In the example depicted in FIG. 63 , the selected data type, “Menstruation Sample,” corresponds to data that can be entered for the “Menstrual Flow” sub-category. Interface 6300 includes data value picker 6304 to enable the user to pick a value for the menstruation sample. In this example, possible values that may be picked include Light, Medium, and Heavy. Restated, “Menstruation Sample” takes on values from a discrete set of values listed in picker 6304.

Interface 6300 also includes option 6306 for entering a date associated with the menstruation sample, and option 6308 for indicating whether the date is the start of the menstrual cycle. Information regarding the start of a particular cycle is useful for determining the range of a period of wellness activity. For example, information entered via option 6308 is used to derive the position of marker 5828 representing the beginning of a menstrual flow (FIG. 58C) in some examples.

FIG. 38A illustrates an example process 3800 for managing and displaying wellness or non-wellness data according to various examples. Process 3800 can be performed at an electronic device (e.g., device 610) with a display. In some examples, the display can include a touch-sensitive display. In other examples, the display can be separate from a touch-sensitive surface. Some blocks of process 3800 can be combined and/or the order of some blocks can be changed.

As described below, process 3800 provides an intuitive way to manage sources and destinations of data stored in wellness database 611. The process allows a user to specify which devices and applications can access data in wellness database 611, as well as to specify the devices and applications that can serve as sources for data to be stored in wellness database 611. Additionally, for the sources, the user can specify what types of data those sources can provide and which sources take priority over others. This can be advantageous when one device is more likely to produce more accurate results than another.

At block 3802, information identifying a plurality of approved sources of wellness data can be received by a user device (e.g., user device 610) from a user. In some examples, the information identifying the plurality of approved sources can identify one or more types of wellness or non-wellness data that are approved to be received from the plurality of approved sources and stored in a wellness database (e.g., wellness database 611). For example, the information identifying the plurality of approved sources can be received via an interface similar or identical to interfaces 3500, 3600, and 3700. In these examples, a user can specify which types of data can be provided by each of the plurality of approved sources to be stored in the wellness database.

At block 3804, information identifying a plurality of approved destinations of wellness or non-wellness data can be received by a user device (e.g., user device 610) from the user. For example, the information identifying the plurality of approved destinations can be received via an interface similar or identical to interface 3500. In these examples, a user can specify which destinations are approved to access data from the wellness database.

In some examples, the plurality of approved sources can include an electronic device or a software application. For example, an approved electronic device, such as a watch, a mobile phone, or the like, can provide wellness or non-wellness data to user device 610 to be stored in wellness database 611. Similarly, an approved software application on or otherwise associated with user device 610 can provide wellness or non-wellness data to user device 611 to be stored in wellness database 611. In some examples, the approved software application can be a software application associated with an electronic device and is capable of communicating with the electronic device.

Similarly, in some examples, the plurality of approved destinations can include an electronic device or a software application. For example, an approved electronic device, such as a watch, a mobile phone, or the like, can access wellness or non-wellness data stored in wellness database 611. Similarly, an approved software application on or otherwise associated with user device 610 can access wellness or non-wellness data stored in wellness database 611. In some examples, the approved software application can be a software application associated with an electronic device and is capable of communicating with the electronic device.

In some examples, the plurality of approved sources can be ranked amongst each other. In some examples, an interface similar or identical to interface 3500 can be used to display and adjust the relative ranking of the approved sources. For example, as shown in interface 3500, Device 1 can be ranked higher than Device 2 to prioritize data from Device 1 over data from Device 2, and Device 2 can be ranked higher than App 3 to prioritize data from Device 1 and Device 2 over data from App 3.

In some examples, process 3800 can further include, at block 3806, identifying a first wellness data entry and a second wellness data entry that are duplicates of one another. In some examples, this can include identifying a first wellness data entry in the wellness database that was received from a first approved source of the plurality of approved sources, the first wellness data entry comprising a first wellness data type and a first timestamp, and identifying a second wellness data entry in the wellness database that was received from a second approved source of the plurality of approved sources, the second wellness data entry comprising a second wellness data type and a second timestamp, wherein the first wellness data type and the second wellness data type are the same, and wherein the first timestamp is within a threshold length of time from the second timestamp. For example, a first data entry can have a type of “step data” and an associated timestamp of 2:30 p.m. on Mar. 1, 2014. The second data entry can have a type of “step data” and an associated timestamp of 2:31 p.m. on Mar. 1, 2014. If the threshold length of time used at block 3806 is 5 minutes, it can be determined that the first data entry and the second data entry are of the same data type and include timestamps that are within a threshold length of time from each other. This can indicate that the first data entry and the second data entry are likely duplicate entries representing the same actions performed by the user.

At block 3808, one of the first data entry and the second data entry can be prioritized or otherwise identified as being preferred over the other based on a ranking of the plurality of sources. For example, as discussed above, the plurality of approved sources can be ranked amongst each other (e.g., as shown in interface 3500). In some examples, if the first approved source providing the first data entry is identified by the user as being preferred over the second approved source, block 3808 can include using the first wellness data entry instead of using the second wellness data entry. For example, this can include deleting the second data entry from wellness database 611 or otherwise ignoring the second data entry for purposes of being displayed or presented to the user. In other examples, if the first approved source has been identified by the user as being preferred over the second approved source, then block 3806 can include prioritizing the first wellness data entry over the second wellness data entry. A data entry that is prioritized over another can be used in place of the other (e.g., displayed, used in calculations, or the like in favor of the other data entry).

In other examples, if the second approved source has been identified by the user as being preferred over the first approved source, then block 3806 can include prioritizing the second wellness data entry over the first wellness data entry. A data entry that is prioritized over another can be used in place of the other (e.g., displayed, used in calculations, or the like in favor of the other data entry).

In some examples, as shown in FIG. 38B, process 3800 can further include, at block 3810, displaying, by the electronic device on the display, a plurality of categories of wellness data stored in the wellness database. For example, an interface similar or identical to interface 2800 can be displayed. The interface can include any amount or any type of categories of wellness or non-wellness data.

At block 3812, a selection of a category of wellness data from the displayed plurality of categories of wellness data can be detected at the electronic device. For example, a selection of one of the categories displayed in an interface similar or identical to interface 2800 made via a touch event by a finger or other device on a touch sensitive display, a click of a mouse or other device, a touch event on a touch pad, or the like, can be detected. In some examples, each of the displayed plurality of categories can include an indicator (e.g., indicator 2804) that can be color-coded based on the type of wellness or non-wellness data of the category. For example, the indicator associated with “Fitness” can have a different color than the indicator associated with “Vital Signs.”

At block 3814, one or more sub-categories of the category of wellness data can be displayed in response to detecting the selection of the category of wellness data. For example, an interface similar or identical to interface 2900 containing a list of sub-categories falling within the category selected at block 3812 can be displayed. In some examples, the displayed interface can include indicators that can be color-cored based on the type of wellness or non-wellness data that it represents.

At block 3816 a selection of a sub-category from the displayed one or more sub-categories can be detected. For example, a selection of one of the sub-categories displayed in an interface similar or identical to interface 2900 made via a touch event by a finger or other device on a touch sensitive display, a click of a mouse or other device, a touch event on a touch pad, or the like, can be detected.

At block 3818, a detailed view of the selected sub-category can be displayed in response to detecting the selection of the sub-category at block 3816. For example, an interface similar or identical to interface 3200 can be displayed. The detailed view of the sub-category can include a graphical representation of the sub-category of data (e.g., graph 3102) and a numerical daily value (e.g., daily value 3104). The detailed view can further include options to show all data (e.g., option 3106), add a data point (e.g., option 3108), share data (e.g., option 3110), and show on dashboard (e.g., option 3112). The detailed view can further include a graphic representation of the sub-category (e.g., graphic 3114) and a text description of the sub-category (e.g., description 3122),

In some examples, process 3800 can include displaying an interface similar or identical to interface 3400 in response to a selection of the add a data point option (e.g., option 3108). The interface can include one or more input fields (e.g., fields 3402, 3404, and 3406) for entering information associated with the wellness data entry. In some examples, process 3800 can further include receiving a wellness data entry to be stored in the wellness database that was input into the input field (e.g., input into fields 3402, 3404, and 3406).

In some examples, process 3800 can further include displaying an interface similar or identical to interface 3300 in response to a selection of the show all data option (e.g., option 3106). The interface can include a plurality of wellness data entries corresponding to the sub-category stored in the wellness database (e.g., entries in list 3302) In some examples, each of the plurality of wellness data entries can include a numerical value of the data entry, a timestamp, and an identification of a source of the data entry (e.g., indicator 3304).

In some examples, process 3800 can further include displaying a data sharing interface similar or identical to interface 3500 in response to a selection of the share data option (e.g., option 3110). The interface can include the plurality of approved sources (e.g., source list 3506) and the plurality of approved destinations (e.g., list 3504). In some examples, a request to reorder the displayed plurality of approved sources can be detected by the electronic device. For example, a selection of edit button 3508 can be received and movement of one or more of the sources in source list 3506 can be detected. In response to detecting the request to reorder the displayed plurality of approved sources, the displayed plurality of approved sources can be reordered in accordance with the detected request to reorder the displayed plurality of approved sources

In some examples, the data sharing interface (e.g., interface 3500) can further include options to add an approved destination to the plurality of approved destinations and to remove an approved destination from the plurality of approved destinations (e.g., options 3512, 3514, 3516, and 3518).

In some examples, process 3800 can further include receiving, at the electronic device, a search query. In response, one or more sub-categories of the plurality of categories that match the search query can be displayed. The displayed one or more sub-categories that match the search query can be color-coded based on their respective categories. For example, a search query can be received from a search box (e.g., search box 2808) displayed within an interface similar or identical to interface 2800 or 2900. A search results interface similar or identical to interface 3000 can be displayed in response to the search query. The search results interface can include the one or more sub-categories that match the search query.

In some examples, process 3800 can further include displaying, on the display, a source interface comprising a list of known sources. For example, an interface similar or identical to interface 3600 can be displayed having a list of known sources (e.g., list 3606). The source interface can further include a numerical indicator associated a known source of the known sources that represents a number of new types of wellness data that can be provided by the known source. For example, the number “2” is shown for Device 1, indicating the two new types of data (e.g., Calories burned and flights of stairs climbed) are available.

In some examples, process 3800 can further include detecting a selection of a known source from the list of displayed sources. In response to detecting the selection of the known source, a list of types of wellness data that the known source can provide can be displayed. For example, a source from source list 3606 of interface 3600 can be received by a user selecting an option 3610 associated with the source. In response, an interface similar or identical to interface 3700 can be displayed. The displayed interface can include a list (e.g., list 3706) of known types of data that the source can provide. In some examples, the list of types of wellness data that the known source can provide can include a selectable option (e.g., options 3704, 3708, 3710, 3712, and 3714) for each of the types of wellness data that the known source can provide to approve or reject the associated type of wellness data.

In some examples, process 3800 can further include detecting a selection of the selectable option for a type of wellness data that the known source can provide at the electronic device. In response to detecting the selection of the selectable option, process 3800 can further include approving or rejecting the type of wellness data that the known source can provide in accordance with the detected selection of the selectable option. For example, user device 610 can accept or reject the types of wellness data shown in interface 3700 based on the positions of the switches of options 3704, 3708, 3710, 3712, and 3714.

It should be understood that the particular order in which the operations in FIGS. 38A and 38B have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other processes described herein (e.g., processes 800, 1500, 1700, 2000, 2700, or 4400) are also applicable in an analogous manner to process 3800 described above with respect to FIGS. 38A and 38B. For brevity, these details are not repeated here.

Medical Identification Information

FIG. 39 illustrates one example lock screen interface 3900 that can be displayed by user device 610 while the user device is in a locked state. In some examples, the locked state can represent a state in which user device 610 restricts one or more functions from being performed. For example, user device 610 can prevent a user from running applications, changing settings, or the like, while in the locked state. In other examples, the locked state can represent a state in which user device 610 additionally or alternatively prevents access at least a subset of data stored on the device. For example, user device 610 can prevent a user from viewing photos or videos, accessing documents, or the like, while in the locked state. In other examples, the locked state can represent a state in which user device 610 additionally or alternatively restricts communications from the electronic device. For example, user device 610 can prevent a user from sending SMS messages or emails, or making calls to non-emergency phone numbers.

As shown in FIG. 39 , lock screen interface 3900 can include the current date and time. Lock screen interface 3900 can further be responsive to user input to allow a user to unlock the device. For example, a swiping gesture can cause user device 610 to display a numerical input pad to allow the user to enter a passcode to unlock the device. Lock screen interface 3900 can further include emergency option 3902 for accessing emergency features of user device 610. For example, FIG. 40 illustrates an example emergency dialing interface 4000 that can be displayed in response to a selection of emergency option 3902. As shown, emergency dialing interface 4000 can include numerical input pad 4004 for allowing a temporary user to enter an emergency phone number to dial while the device is in the locked state. In some examples, user device 610 can call a number entered using input pad 4004 if the entered number is predefined phone number (e.g., 9-1-1). In some examples, the temporary user can be a first responder or other person that encounters the primary user of the device when the primary user of the device is unable to operate user device 610 (e.g., because the primary user is unconscious or injured). Thus, emergency dialing interface 4000 allows the temporary user to place calls to predetermined emergency phone numbers without requiring the temporary user to unlock user device 610.

Interface 4000 can further include Medical ID or emergency information option 4002 for viewing medical information associated with a user by the temporary user. In this example, the user can be a primary user or owner of user device 610 that has customized the device by installing applications and/or entering personal information to user device 610. Thus, Medical ID or emergency information option 4002 can be selected by the temporary user to view emergency information associated with the primary user without requiring the temporary user to unlock user device 610.

For example, FIG. 41 illustrates an example emergency information interface 4100 that can be displayed in response to a selection of Medical ID or emergency information option 4002 in interface 4000. As shown, interface 4100 can include user information 4102 including the user's name and birthdate. Interface 4100 can further include a free-form field 4104 that can be used to store and display a description of any medical conditions that the user may have. Interface 4100 can further include a free-form field 4106 that can be used to store and display any other relevant medical notes about the user. Interface 4100 can further include free-form field 4108 that can be used to store and display a description of any allergies or reactions that the user may have to drugs or any other substance. Interface 4100 can further include free-form field 4110 that can be used to store and display a description of any medications that the user may be taking or that the user may require.

Interface 4100 can further include emergency contacts 4112. Emergency contacts 4112 can include a list of one or more people that the user has designated as being his/her emergency contact. Emergency contacts 4112 can include a name of each emergency contact and a relationship between the user and the emergency contact. For example, one entry for an emergency contact can include the name “Jane Smith” having a relationship with the user of “mother.” In some examples, emergency contacts 4112 can further include contact information for the emergency contact, such as a phone number, email address, or the like. In other examples, emergency contact 4112 can exclude contact information for the emergency contact, such as a phone number, email address, or the like. This can be done to protect the privacy of the emergency contact. In either example, user device 610 can allow a temporary user to select one of the displayed emergency contacts to initiate communication with that contact (even if the phone number of the emergency contact is not displayed) while user device 610 remains in the locked state. For example, in response to a selection of one of the emergency contacts, user device 610 can initiate a phone call to the contact, send an SMS message to the contact, send an email to the emergency contact, or the like, while the device remains in the locked state. In some examples, when user device 610 initiates a call to an emergency contact in response to a selection of that emergency contact, user device 610 can flag the call as being an emergency call. In some examples, emergency calls can be accepted by a receiving device in any state of operation. For example, a call flagged as being an emergency call can cause the receiving device to ring while in a do-not-disturb mode, a silent mode, or the like. Additionally, an indicator can be displayed on the receiving device notifying the recipient that the call is an emergency call.

In some examples, a primary user can create their medical identification from the contact list of user device 610. For example, FIG. 42 illustrates an example interface 4200 that can be displayed to display the user's contact list. As shown, interface 4200 can include a “Create Medical ID” button 4202 for creating a medical identification. FIG. 43 illustrates an example interface 4300 that can be displayed in response to a selection of button 4202. As shown, interface 4300 includes a text description 4302 that can provide information about the medical identification, such as the purpose of the medical identification, the privacy settings for information contained in the medical identification, and the like.

FIG. 44 illustrates an example interface 4400 that can be displayed in response to a user accepting or acknowledging the contents of description 4302 in interface 4300. As shown, interface 4400 can include user information 4402 that can correspond to user information 4102 in interface 4100. In some examples, this information can be auto-populated by user device 610 based on information previously known about the user. In other examples, the user can enter this information manually. Interface 4400 can further include free-form text fields 4404, 4406, 4408, and 4410 that can correspond to fields 4104, 4106, 4108, and 4110 of interface 4100. Thus, information entered into fields 4404, 4406, 4408, and 4410 can be displayed in fields 4104, 4106, 4108, and 4110 of interface 4100. Interface 4400 can further include contacts 4412 to allow a user to enter one or more emergency contacts. In some examples, the one or more emergency contacts can be selected from the user's contact list on user device 610. In other examples, the one or more emergency contacts can be entered manually by the user. In yet other examples, the emergency contact can be selected from the user's contact list on user device 610 and additional information (e.g., relationship information) can be manually added by the user. Interface 4400 can further include “Show Medical ID” option 4414 having selectable option 4416. The position of the switch of option 4416 can be used to turn on or off the showing of the user's medical information while the device is in the locked state. For example, when moved to the right, as shown in FIG. 44 , the switch of option 4416 can cause user device 610 to display option 4002 in the emergency dialing interface 4000 and to display interface 4100 in response to a selection of option 4002. However, when moved to the left, the switch of option 4416 can prevent user device 610 from displaying option 4002 in the emergency dialing interface 4000 and can prevent user device 610 from displaying interface 4100 in response to a selection of option 4002.

FIG. 45 illustrates an exemplary process 4500 for displaying medical information on a locked device. Process 4500 can be performed at an electronic device (e.g., device 610) with a display. In some examples, the display can include a touch-sensitive display. In other examples, the display can be separate from a touch-sensitive surface. Some blocks of process 4500 can be combined and/or the order of some blocks can be changed.

As described below, process 4500 provides a way for a temporary user to view medical information associated with a primary user or owner of an electronic device while the device remains in a locked state. Process 4500 also allows a temporary user to initiate communication with the primary user's emergency contacts while the device remains in the locked state. This advantageously allows a temporary user that finds the primary user (e.g., in a state in which the primary user is unable to operate the electronic device or communicate) to assist the primary user in getting the appropriate medical care.

At block 4502, at an electronic device (e.g., user device 610) while the electronic device is in a locked state, a request to display emergency information about a user of the device can be detected. For example, the request to display the emergency information can be received while an emergency dialing interface similar or identical to interface 4000 is being displayed, and the request can include a selection of an emergency information option similar or identical to option 4002. The emergency information about the user of the device can include the user's name, birthday, medical conditions, allergies and reactions, medications, and one or more emergency contacts of the user. As discussed above, the user can be a primary user or owner of user device 610 that has customized the device by installing applications and/or entering personal information to user device 610. The request to display the medical information can be made by a temporary user, such as a first responder or other person that encounters the primary user of the device when the primary user of the device is unable to operate user device 610 (e.g., because the primary user is unconscious or injured).

At block 4504, in response to detecting the request, an emergency information interface comprising emergency information about the user of the device can be displayed without unlocking the device. For example, an interface similar or identical to interface 4100 can be displayed.

In some examples, the emergency information about the user can include information associated with an emergency contact. The information associated with the emergency contact can include a name of the emergency contact and a relationship between the user and the emergency contact. For example, information about an emergency contact can be displayed in a manner similar or identical to emergency contact 4112 in interface 4100. One example emergency contact can include the contact's name “Jane Smith,” and the relationship “mother” between the user and the contact.

At block 4506, user device 610 can detect a request to communicate with an emergency contact while the electronic device is in the locked state. For example, a selection of a contact 4112 from interface 4100 can be detected.

At block 4508, user device 610 can initiate communication with the emergency contact in response to detecting the request to communicate. In some examples, initiating communication with the emergency contact includes sending an SMS message or email to the emergency contact. In other examples, initiating communication with the emergency contact can include calling a phone number associated with the emergency contact. In some examples, calling the phone number associated with the emergency contact can include flagging the call to the phone number as an emergency call. In some examples, the phone number associated with the emergency contact can be included in the information associated with the emergency contact displayed within the emergency information interface (e.g., interface 4100). In other examples, the phone number associated with the emergency contact may not be included in the information associated with the emergency contact displayed within the emergency information interface (e.g., interface 4100). However, a call or other communication can still be made to this emergency contact. This can be done to protect the privacy of the emergency contact.

In some examples, process 4500 can include displaying an emergency dialing interface prior to displaying the emergency information interface. The emergency dialing interface can include a numerical input pad and an emergency information option. For example, an emergency dialing interface similar or identical to interface 4000 can be displayed prior to displaying emergency information interface 4100. The emergency dialing interface 4000 can include a numerical input pad similar or identical to input pad 4004 and an emergency information option similar or identical to option 4002. In some examples, the emergency information interface (e.g., interface 4100) can be displayed in response to a selection of the emergency information option (e.g., option 4002).

In some examples, process 4500 can further include detecting a predefined phone number entered using the numerical input pad while the electronic device is in the locked state. In response to detecting the predefined phone number, process 4500 can further include calling the predefined phone number. For example, user device 610 can detect a predefined number (e.g., 9-1-1) entered in the numerical input pad (e.g., input pad 4004). In response to detecting the predefined phone number, user device 610 can call the predefined number while still in the locked state. In some examples, calling the predefined phone number can include flagging the call to the predefined phone number as an emergency call.

In some examples, calls flagged as being emergency calls can be accepted by a receiving electronic device in any state of operation. For example, a call flagged as being an emergency call can cause the receiving device to ring while in a do-not-disturb mode, a silent mode, or the like. Additionally, an indicator can be displayed on the receiving device notifying the recipient that the call is an emergency call.

In some examples, process 4500 can further include displaying a lock screen interface comprising an emergency option prior to displaying the emergency dialing interface. For example, an interface similar or identical to interface 3900 can be displayed having an emergency option similar or identical to option 3902. The lock screen interface can further include one or more controls for unlocking the device. For example, a numerical input pad can be displayed to allow a user to enter a passcode, or user device 610 can be configured to detect predefined gestures to unlock the device. In these examples process 4500 can further include detecting a selection of the emergency option and displaying the emergency dialing interface in response to detecting the selection of the emergency option. For example, user device 610 can detect a selection of option 3902 and display interface 4000 in response to detecting the selection of option 3902.

It should be understood that the particular order in which the operations in FIG. 45 have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other processes described herein (e.g., processes 900, 1600, 1800, 2100, 2700, or 3800) are also applicable in an analogous manner to process 4500 described above with respect to FIG. 45 . For brevity, these details are not repeated here.

In some examples, the interfaces shown in FIGS. 22-23, 28-36, 41-43, and 56-59 can include menu bar 2250 for navigating between the various interfaces. For example, in response to a selection of “Dashboard” in menu 2250, interface 2100 or 2200 can be displayed. In response to a selection of “My Health” in menu 2250, interface 2700 can be displayed. In response to a selection of “Medical ID” in menu 2250, interface 4400 can be displayed. In response to a selection of “Settings” in menu 2250, interface 3600 can be displayed.

One or more of the functions relating to aggregating and sharing wellness data can be performed by a system similar or identical to system 4600 shown in FIG. 46 . System 4600 can include instructions stored in a non-transitory computer readable storage medium, such as memory 4604 or storage device 4602, and executed by processor 4606. The instructions can also be stored and/or transported within any non-transitory computer readable storage medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “non-transitory computer readable storage medium” can be any medium that can contain or store the program for use by or in connection with the instruction execution system, apparatus, or device. The non-transitory computer readable storage medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, a portable computer diskette (magnetic), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM) (magnetic), a portable optical disc such a CD, CD-R, CD-RW, DVD, DVD-R, or DVD-RW, or flash memory such as compact flash cards, secured digital cards, USB memory devices, memory sticks, and the like.

The instructions can also be propagated within any transport medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “transport medium” can be any medium that can communicate, propagate or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The transport medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic or infrared wired or wireless propagation medium.

In some examples, system 4600 can be included within user device 610 or user server 614. Processor 4606 can be configured to perform processes 800, 900, 1500, 1800, 2100, 2700, 3800, or 4500. It is to be understood that the system is not limited to the components and configuration of FIG. 46 , but can include other or additional components in multiple configurations according to various examples.

In accordance with some examples, FIG. 47 shows a functional block diagram of an electronic device 4700 configured in accordance with the principles of the various described examples. The functional blocks of the device can be implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 47 can be combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 47 , electronic device 4700 can include a display unit 4704 for displaying a user interface and, optionally, sensor units 4702 configured to receive touch input. Electronic device 4700 can further include a processing unit 4708 coupled to the optional sensor units 4702 and display unit 4704. In some examples, processing unit 4708 can include one or more of a display enabling unit 4710, a receiving unit 4712, and a generating unit 4714.

Processing unit 4708 may be configured to: enable display (e.g., with display enabling unit 4710) of an aggregated view of a plurality of types of wellness data, wherein the aggregated view comprises a plurality of partitions, each partition of the plurality of partitions associated with a type of the plurality of types of wellness data; receive (e.g., with receiving unit 4712) a selection of a partition of the plurality of partitions; and enable display (e.g., with display enabling unit 4710) of an expanded view of the selected partition of the plurality of partitions.

In some embodiments, in the aggregated view, each partition of the plurality of partitions comprises an identifier of an associated type of wellness data and a first portion of the associated type of wellness data displayed therewith, and wherein the expanded view comprises a larger view of the selected partition of the plurality of partitions and a second portion of the associated type of wellness data displayed therewith.

In some embodiments, the first portion of the wellness data comprises a most recent value of the associated type of wellness data, and wherein the second portion of the associated type of wellness data comprises a representation of the associated type of wellness data over time.

In some embodiments, the processing unit is configured to: enable the display (e.g., with display enabling unit 4710) of the expanded view of the selected partition by at least enabling the display of a collapsed set of partitions representing partitions of the plurality of partitions that were not selected.

In some embodiments, the plurality of partitions are ordered within the display based on a frequency of use of an associated type of wellness data, a time of most recently added value of the associated type of wellness data, or a time of day.

In some embodiments, the expanded view of the selected partition comprises a selectable element to share the wellness data associated with the partition through email or text message.

In some embodiments, the plurality of types of wellness data comprises weight data, blood sugar data, blood pressure data, activity data, or heart rate data.

In some embodiments, the electronic device further includes a plurality of sensor units coupled to the processing unit 4708 and the display unit 4704. The processing unit 4708 is further configured to generate (e.g., with generating unit 4714) at least one of the plurality of types of wellness data from sensor data obtained from the plurality of sensors.

In some embodiments, the expanded view comprises a graph of the associated type of wellness data, and wherein the graph comprises segments generated from wellness data obtained from different sensors.

In some embodiments, a partition of the plurality of partitions is a user-generated partition.

In some embodiments, the plurality of partitions have the appearance of a plurality of cards displayed in a stack.

The operations described above with reference to FIG. 16 are, optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 47 . For example, displaying operations 1602 and 1606 and receiving operation 1604 may be implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136. A respective event recognizer 180 of application 136 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub event, such as activation of an affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A-1B.

In accordance with some examples, FIG. 48 shows a functional block diagram of an electronic device 4800 configured in accordance with the principles of the various described examples. The functional blocks of the device can be implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 48 can be combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 48 , electronic device 4800 can include a display unit 4802 for displaying a user interface and, optionally, a gyroscope and/or accelerometer unit 4810. Electronic device 4800 can further include a processing unit 4804 coupled to the display unit 4802 and optionally, to the gyroscope and/or accelerometer unit 4810. In some examples, processing unit 4804 can include one or more of a display enabling unit 4806, a selecting unit 4808, a detecting unit 4812, and an identifying unit 4814.

Processing unit 4804 may be configured to: enable display (e.g., with display enabling unit 4806) of a plurality of partitions, wherein each partition of the plurality of partitions is associated with a type of wellness data of a plurality of types of wellness data; in response to detecting a change in an orientation of the device, select (e.g., with selecting unit 4808) a subset of the plurality of partitions; and enable display (e.g., with display enabling unit 4806) of the selected subset of the plurality of partitions.

In some embodiments, the electronic device further includes a gyroscope and/or accelerometer unit 4810 coupled to the processing unit 4804 which is further configured to: detect (e.g., with detecting unit 4812) the change in orientation of the device based on data from the gyroscope and/or accelerometer unit.

In some embodiments, the processing unit is further configured to: detect (e.g., with detecting unit 4812) the change in the orientation of the device by at least detecting a threshold amount of change in the orientation of the electronic device.

In some embodiments, each of the displayed subset of the plurality of partitions comprises a graph representation of at least a portion of the associated type of wellness data displayed therewith.

In some embodiments, the processing unit is further configured to: select (e.g., with selecting unit 4808) a subset of the plurality of partitions by at least: identifying (e.g., with identifying unit 4814) correlations between the plurality of types of wellness data; and selecting (e.g., with selecting unit 4808) partitions associated with correlated types of wellness data as the subset of the plurality of partitions.

The operations described above with reference to FIG. 18 are, optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 48 . For example, displaying operations 1802 and 1808 and detecting operation 1804 may be implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136. A respective event recognizer 180 of application 136 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub event, such as activation of an affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A-1B.

In accordance with some examples, FIG. 49 shows a functional block diagram of an electronic device 4900 configured in accordance with the principles of the various described examples. The functional blocks of the device can be implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 49 can be combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 49 , electronic device 4900 can include a display unit 4902 for displaying a user interface. Electronic device 4900 can further include a processing unit 4904 coupled to the display unit 4902. In some examples, processing unit 4904 can include a display causing unit 4906 and a receiving unit 4908.

Processing unit 4904 may be configured to: cause display (e.g., with display causing unit 4806) of a first plurality of partitions associated with a first user, wherein each partition of the first plurality of partitions is associated with a type of wellness data of the first user; and in response to receiving a request (e.g., with receiving unit 4908) to view a second plurality of partitions associated with a second user, cause a display (e.g., with display causing unit 4906) of a second plurality of partitions associated with a second user, wherein each partition of the second plurality of partitions is associated with a type of wellness data of the second user.

In some embodiments, the request to view the second plurality of partitions comprises a request to scroll the displayed first plurality of partitions in a lateral direction.

In some embodiments, the request to view the second plurality of partitions comprises a selection of the second user from a list of users.

In some embodiments, the first user has been authorized by the second user to view the second plurality of partitions.

The operations described above with reference to FIG. 21 are, optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 49 . For example, displaying operations 2102 and 2106 and receiving operation 2104 may be implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136. A respective event recognizer 180 of application 136 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub event, such as activation of an affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A-1B.

In accordance with some examples, FIG. 50 shows a functional block diagram of an electronic device 5000 configured in accordance with the principles of the various described examples. The functional blocks of the device can be implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 50 can be combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 50 , electronic device 5000 can include a display unit 5002 for displaying a user interface. Electronic device 5000 can further include a processing unit 5004 coupled to the display unit 5002. In some examples, processing unit 5004 can include a receiving unit 5006 and a transmitting unit 5008.

Processing unit 5004 may be configured to: receive (e.g., with receiving unit 5006) an identification of a user authorized to access a set of wellness data; in response to detecting an update to the set of wellness data, transmit (e.g., with transmitting unit 5008) a notification to the user authorized to access the set of wellness data notifying the user authorized to access the set of wellness data that the update to the set of wellness data has been detected; and transmit (e.g., with transmitting unit 5108) at least a portion of the set of wellness data to the user authorized to access the set of wellness data.

In some embodiments, the identification of the user authorized to access the set of wellness data comprises a name, a username, or contact information.

In some embodiments, the at least a portion of the set of wellness data is transmitted in response to receiving a request from the user authorized to access the set of wellness data.

The operations described above with reference to FIG. 8 are, optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 50 . For example, receiving operation 802 and transmitting operations 806 and 808 may be implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136. A respective event recognizer 180 of application 136 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub event, such as activation of an affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A-1B.

In accordance with some examples, FIG. 51 shows a functional block diagram of an electronic device 5100 configured in accordance with the principles of the various described examples. The functional blocks of the device can be implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 51 can be combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 51 , electronic device 5100 can include a display unit 5102 for displaying a user interface. Electronic device 5100 can further include a processing unit 5104 coupled to the display unit 5102. In some examples, processing unit 5104 can include one or more of a receiving unit 5106 and a transmitting unit 5108.

Processing unit 5104 may be configured to: receive (e.g., with receiving unit 5106), from a first user, a request to access wellness data associated with a second user; transmit (e.g., with transmitting unit 5108), to the second user, a request to authorize the first user to access the wellness data associated with the second user; and in response to receiving an authorization from the second user, transmit (e.g., with transmitting unit 5108) the wellness data associated with the second user to the first user.

In some embodiments, the first user is a health care provider and the second user is a patient, and wherein the request to access the wellness data associated with the second user is received prior to an appointment between the first user and the second user.

In some embodiments, the request to authorize the first user to access the wellness data associated with the second user is displayed on a mobile device of the second user.

The operations described above with reference to FIG. 9 are, optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 51 . For example, receiving operation 902 and transmitting operations 904 and 908 may be implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136. A respective event recognizer 180 of application 136 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub event, such as activation of an affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A-1B.

In accordance with some examples, FIG. 52 shows a functional block diagram of an electronic device 5200 configured in accordance with the principles of the various described examples. The functional blocks of the device can be implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 52 can be combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 52 , electronic device 5200 can include a display unit 5202 for displaying a user interface. Electronic device 5200 can further include a processing unit 5204 coupled to the display unit 5202. In some examples, processing unit 5204 can include one or more of a display enabling unit 5206, a detecting unit 5208, a scroll enabling unit 5210, and a reordering unit 5212.

Processing unit 5204 may be configured to: enable display (e.g., with displaying enabling unit 5206) of, on the display, a graph comprising a first data-set representation of a first data set in which a first dependent variable varies as an independent variable changes and a second data-set representation of a second data set in which a second dependent variable varies as the independent variable changes, wherein the first data-set representation is associated with a first range of vertical positions within the graph and the second data-set representation is associated with a second range of vertical positions within the graph; detect (e.g., with detecting unit 2108), at a respective location on the display, a user input; in response to detecting the user input: in accordance with a determination that the respective location is within the first range of vertical positions associated with the first data-set representation, enable display (e.g., with display enabling unit 5206) of, on the display, an indication that the first data-set representation has been selected; and in accordance with a determination that the respective location is within the second range of vertical positions associated with the second data-set representation, enable display (e.g., with display enabling unit 5206) of, on the display, an indication that the second data-set representation has been selected.

In some embodiments, the processing unit 5204 is further configured to: enable display (e.g., with display enabling unit 5206) of the first data-set representation in the graph overlapping the second data-set representation.

In some embodiments, the first data set comprises a first set of wellness data, and wherein the second data set comprises a second set of wellness data.

In some embodiments, the first range of vertical positions is uniquely associated with the first data-set representation, and wherein the second range of vertical positions is uniquely associated with the second data-set representation.

In some embodiments, the first data-set representation and the second data-set representation are colored-coded based on a type of data that they represent.

In some embodiments, processing unit 5204 is further configured to: enable display (e.g., with display enabling unit 5206) of the indication that the first data-set representation has been selected by at least enabling display, on the display, of a marker overlaid on the first data-set representation at a horizontal position corresponding to a horizontal position of the respective location on the display.

In some embodiments, processing unit 5204 is further configured to enable display (e.g., with display enabling unit 5206) of the indication that the second data-set representation has been selected by at least enabling display, on the display, of a marker overlaid on the second data-set representation at a horizontal position corresponding to a horizontal position of the respective location on the display.

In some embodiments, processing unit 5204 is configured to enable display (e.g., with display enabling unit 5206) of the indication that the first data-set representation has been selected by at least enabling display, on the display, of a numerical value of a first data entry of the first data set associated with a value of the independent variable corresponding to a horizontal position of the respective location on the display.

In some embodiments, processing unit 5204 is further configured to: enable display (e.g., with display enabling unit 5206) of the indication that the second data-set representation has been selected by at least enabling display, on the display, of a numerical value of a second data entry of the second data set associated with a value of the independent variable corresponding to a horizontal position of the respective location on the display.

In some embodiments, the first data set or the second data set comprises blood pressure data, and wherein the numerical value of the first data entry or the second data entry comprises a high value for diastolic blood pressure, a low value for diastolic blood pressure, a high value for systolic blood pressure, and a low value for systolic blood pressure.

In some embodiments, the first data-set representation or the second data-set representation is generated based on an average of blood pressure values.

In some embodiments, the first data set or the second data set comprises heart rate data, and wherein the numerical value of the first data entry or the second data entry comprises a high value for heart rate and a low value for heart rate.

In some embodiments, the first data-set representation comprises a first line in the graph, and wherein displaying the indication that the first data-set representation has been selected comprises highlighting an area below the first line.

In some embodiments, the second data-set representation comprises a second line in the graph, and wherein displaying the indication that the second data-set representation has been selected comprises highlighting an area below the second line.

In some embodiments, the first range of vertical positions within the graph expands based on a length of time that the user input is detected while a vertical position of the respective location on the display is within the first range of vertical positions, and wherein the second range of vertical positions within the graph expands based on a length of time that the user input is detected while the vertical position of the respective location on the display is within the second range of vertical positions.

In some embodiments, the dependent variable for the first data set is measured in different units from the dependent variable for the second data set.

In some embodiments, a vertical scale for displaying the first data-set representation is different from a vertical scale for displaying the second data-set representation.

In some embodiments, the vertical scale for the first data-set representation is determined based on the maximum and minimum values of the first dependent variable of the first data-set representation that are to be displayed in the graph, and wherein the vertical scale for the second data-set representation is determined based on the maximum and minimum values of the second dependent variable of the second data-set representation that are to be displayed in the graph.

In some embodiments, the vertical scale for the first data-set representation of the plurality of sets of wellness data is defined by: a maximum vertical position within the graph corresponding to a first multiplying factor multiplied by the maximum value of the first dependent variable of the first data-set representation that are to be displayed in the graph; and a minimum vertical position within the graph corresponding to a second multiplying factor multiplied by the minimum value of the first dependent variable of the first data-set representation that are to be displayed in the graph.

In some embodiments, the vertical scale for the second data-set representation of the plurality of sets of wellness data is defined by: a maximum vertical position within the graph corresponding to a third multiplying factor multiplied by the maximum value of the second dependent variable of the second data-set representation that are to be displayed in the graph; and a minimum vertical position within the graph corresponding to a fourth multiplying factor multiplied by the minimum value of the second dependent variable of the second data-set representation that are to be displayed in the graph.

In some embodiments, the processing unit 5204 is further configured to: detect (e.g., with detecting unit 5208) detailed-view input; and in response to detecting the detailed-view input, enable display of a detailed view of the first data set and the second data set, wherein the detailed view comprises a first partition associated with the first data set and a second partition associated with the second data set.

In some embodiments, processing unit 5204 is configured to detect (e.g., with detecting unit 5208) the detailed-view input by at least detecting a change in orientation of the electronic device while displaying the graph.

In some embodiments, processing unit 5204 is further configured to: detect (e.g., with detecting unit 5208) a request to scroll the detailed view; and in response to detecting the request to scroll the detailed view, enable scrolling (e.g., with scroll enabling unit 5210) of the detailed view.

In some embodiments, the first partition comprises a first graph representation of the first data set, and wherein the second partition comprises a second graph representation of the second data set.

In some embodiments, the first graph representation is non-overlapping with the second graph representation.

In some embodiments, processing unit 5204 is further configured to: enable display (e.g., with display enabling unit 5206) of the first partition in a color matching a color of the first data-set representation, and wherein the second partition is displayed in a color matching a color of the second data-set representation.

In some embodiments, the processing unit 5204 is configured to: enable display (e.g., with display enabling unit 5206) of the first partition in a color matching a color of the first data-set representation, and enable display of the second partition in a color matching a color of the second data-set representation.

In some embodiments, processing unit 5204 is further configured to: detect (e.g., with detecting unit 5208) a request to reorder the first partition and the second partition; and in response to detecting the request to reorder the first partition and the second partition, reorder (e.g., with reordering unit 5212) the first partition and the second partition within the detailed view.

In some embodiments, processing unit 5204 is further configured to: detect graph-view input; and in response to detecting the graph-view input, display the graph comprising the first data-set representation of the first data set and the second data-set representation of the second data set.

The operations described above with reference to FIG. 27 are, optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 52 . For example, display operation 2702, detection operation 2704, display operation 2706, and display operation 2710 may be implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136. A respective event recognizer 180 of application 136 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub event, such as activation of an affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A-1B.

In accordance with some examples, FIG. 53 shows a functional block diagram of an electronic device 5300 configured in accordance with the principles of the various described examples. The functional blocks of the device can be implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 53 can be combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 53 , electronic device 5300 can include a display unit 5302 for displaying a user interface. Electronic device 5300 can further include a processing unit 5304 coupled to the display unit 5302. In some examples, processing unit 5304 can include one or more of a detecting unit 5306, a display enabling unit 5308, a restricting unit 5310, initiating unit 5312, sending unit 5314, calling unit 5316, and flagging unit 5318.

Processing unit 5304 may be configured to: while the electronic device is in a locked state: detect (e.g., with detecting unit 5306) a request to display emergency information about a user of the device; and in response to detecting the request, enable display (e.g., with display enabling unit 5308), on the display, of an emergency information interface comprising emergency information about the user of the device without unlocking the device.

In some embodiments, processing unit 5304 is further configured to: while the electronic device is in the locked state, restrict (e.g., with restricting unit 5310) use of one or more functions of the electronic device.

In some embodiments, while the electronic device is in the locked state, at least a subset of data stored on the device is not accessible.

In some embodiments, while the electronic device is in the locked state, communications from the electronic device are restricted.

In some embodiments, the emergency information about the user comprises information associated with an emergency contact, and wherein the information associated with the emergency contacts comprises a name of the emergency contact and a relationship between the user and the emergency contact.

In some embodiments, processing unit 5304 is further configured to: detect (e.g., with detecting unit 5306) a request to communicate while the electronic device is in the locked state; and in response to detecting the request to communicate, initiate (e.g., with initiating unit 5312) communication with the emergency contact.

In some embodiments, processing unit 5304 is configured to initiate communication with the emergency contact by at least sending (e.g., with sending unit 5314) an SMS message or email to the emergency contact.

In some embodiments, processing unit 5304 is configured to initiate communication with the emergency contact by at least calling (e.g., with calling unit 5316) a phone number associated with the emergency contact.

In some embodiments, processing unit 5304 is configured to call the phone number associated with the emergency contact by at least flagging (e.g., with flagging unit 5318) the call to the phone number as an emergency call.

In some embodiments, the information associated with the emergency contacts further comprises the phone number associated with the emergency contact.

In some embodiments, the information associated with the emergency contacts excludes the phone number associated with the emergency contact.

In some embodiments, processing unit 5304 is further configured to: prior to displaying the emergency information interface: enable display (e.g., with display enabling unit 5308) of an emergency dialing interface comprising a numerical input pad and an emergency information option; while displaying the emergency dialing interface, detect (e.g., with detecting unit 5306) a selection of the emergency information option; and in response to detecting selection of the emergency information option, enable display (e.g., with display enabling unit 5308) of the emergency information interface.

In some embodiments, processing unit 5304 is further configured to: detect (e.g., with detecting unit 5306) a predefined phone number entered using the numerical input pad while the electronic device is in the locked state; and in response to detecting the predefined phone number, call the predefined phone number.

In some embodiments, processing unit 5304 is configured to call (e.g., with calling unit 5316) the predefined phone number by at least flagging (e.g., with flagging unit 5318) the call to the predefined phone number as an emergency call.

In some embodiments, calls flagged as an emergency call are to be accepted by a receiving electronic device in any state of operation.

In some embodiments, processing unit 5304 is further configured to: prior to displaying the emergency dialing interface: enable display (e.g., with display enabling unit 5308) of a lock screen interface comprising an emergency option; detect (e.g., with detecting unit 5306) a selection of the emergency option; and in response to detecting the selection of the emergency option, enable display (e.g., with display enabling unit 5308) of the emergency dialing interface.

In some embodiments, the emergency information about the user comprises one or more of: the user's name, birthday, medical conditions, allergies and reactions, medications, and one or more emergency contacts of the user.

The operations described above with reference to FIG. 45 are, optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 53 . For example, detection operation 4502 and display operation 4504 may be implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136. A respective event recognizer 180 of application 136 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub event, such as activation of an affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A-1B.

In accordance with some examples, FIG. 54 shows a functional block diagram of an electronic device 5400 configured in accordance with the principles of the various described examples. The functional blocks of the device can be implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 54 can be combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 54 , electronic device 5400 can include a display unit 5402 for displaying a user interface. Electronic device 5400 can further include a processing unit 5404 coupled to the display unit 5402. In some examples, processing unit 5404 can include one or more of a receiving unit 5406, an identifying unit 5408, a using unit 5410, a prioritizing unit 5412, a display enabling unit 5414, a detecting unit 5416, a reordering unit 5418, and an approving or rejecting unit 5420.

Processing unit 5404 may be configured to: receive (e.g., with receiving unit 5406), from a user, information identifying a plurality of approved sources of wellness data, wherein the information identifying the plurality of approved sources identifies one or more types of wellness data that are approved to be received from the plurality of approved sources and stored in a wellness database; and receive (e.g., with receiving unit 5406), from the user, information identifying a plurality of approved destinations of wellness data, wherein the information identifying the plurality of approved destinations identifies one or more types of wellness data that are approved to be accessed from the wellness database by the plurality of approved destinations of wellness data.

In some embodiments, the plurality of approved sources comprises an electronic device or software application.

In some embodiments, the plurality of approved destinations comprises an electronic device or software application.

In some embodiments, the plurality of approved sources is ranked amongst each other.

In some embodiments, processing unit 5404 is further configured to: identify (e.g., with identifying unit 5408) a first wellness data entry in the wellness database that was received from a first approved source of the plurality of approved sources, the first wellness data entry comprising a first wellness data type and a first timestamp; and identify (e.g., with identifying unit 5408) a second wellness data entry in the wellness database that was received from a second approved source of the plurality of approved sources, the second wellness data entry comprising a second wellness data type and a second timestamp, wherein the first wellness data type and the second wellness data type are the same, and wherein the first timestamp is within a threshold length of time from the second timestamp.

In some embodiments, the first approved source has been identified by the user as being preferred over the second approved source, and wherein processing unit 5404 is further configured to: use (e.g., with using unit 5410) the first wellness data entry instead of using the second wellness data entry.

In some embodiments, the first approved source has been identified by the user as being preferred over the second approved source, and wherein processing unit 5404 is further configured to: prioritize (e.g., with prioritizing unit 5412) the first wellness data entry over the second wellness data entry.

In some embodiments, processing unit 5404 is further configured to: in accordance with a determination that the first wellness data entry is prioritized over the second wellness data entry, use (e.g., with using unit 5410) the first wellness data entry instead of using the second wellness data entry.

In some embodiments, the second approved source has been identified by the user as being preferred over the first approved source, and wherein processing unit 5404 is further configured to: prioritize (e.g., with prioritizing unit 5412) the second wellness data entry over the first wellness data entry.

In some embodiments, processing unit 5404 is further configured to: in accordance with a determination that the second wellness data entry is prioritized over the first wellness data entry, use (e.g., with using unit 5410) the second wellness data entry instead of using the first wellness data entry.

In some embodiments, processing unit 5404 is further configured to: enable display (e.g., with display enabling unit 5414), on the display, of a plurality of categories of wellness data stored in the wellness database.

In some embodiments, processing unit 5404 is further configured to: detect (e.g., with detecting unit 5416) a selection of a category of wellness data from the displayed plurality of categories of wellness data; and in response to detecting the selection of the category of wellness data, enable display (e.g., with display enabling unit 5414), on the display, of one or more sub-categories of the category of wellness data.

In some embodiments, processing unit 5404 is further configured to: detect (e.g., with detecting unit 5416) a selection of a sub-category from the displayed one or more sub-categories; and in response to detecting the selection of the sub-category, enable display (e.g., with display enabling unit 5414), on the display, of a detailed view of the sub-category.

In some embodiments, the detailed view of the sub-category comprises a graph representation of the sub-category of wellness data over time and a numerical daily value of the sub-category of wellness data.

In some embodiments, the detailed view of the sub-category further comprises an input field for entering a wellness data entry, and processing unit 5404 is further configured to: receive (e.g., with receiving unit 5406) a wellness data entry to be stored in the wellness database that was input into the input field.

In some embodiments, the detailed view of the sub-category further comprises a textual description of the sub-category.

In some embodiments, the detailed view of the sub-category further comprises an option to view wellness data entries corresponding to the sub-category, and wherein processing unit 5404 is further configured to: enable display (e.g., with display enabling unit 5414), on the display, of a plurality of wellness data entries corresponding to the sub-category stored in the wellness database.

In some embodiments, each of the plurality of wellness data entries comprises a numerical value of the data entry, a timestamp, and an identification of a source of the data entry.

In some embodiments, the detailed view of the sub-category further comprises an option to share wellness data, and processing unit 5404 is further configured to: enable display (e.g., with display enabling unit 5414), on the display, of a data sharing interface comprising the plurality of approved sources and the plurality of approved destinations.

In some embodiments, processing unit 5404 is further configured to: detect (e.g., with detecting unit 5416) a request to reorder the displayed plurality of approved sources; and in response to detecting the request to reorder the displayed plurality of approved sources, reorder (e.g., with reordering unit 5418) the displayed plurality of approved sources in accordance with the detected request to reorder the displayed plurality of approved sources.

In some embodiments, the data sharing interface further comprises options to add an approved destination to the plurality of approved destinations and to remove an approved destination from the plurality of approved destinations.

In some embodiments, processing unit 5404 is further configured to: receive (e.g., with receiving unit 5406) a search query; and enable display (e.g., with display enabling unit 5414), on the display, of one or more sub-categories of the plurality of categories that match the search query, wherein the displayed one or more sub-categories that match the search query are color-coded based on their respective categories.

In some embodiments, processing unit 5404 is further configured to: enable display (e.g., with display enabling unit 5414), on the display, of a source interface comprising a list of known sources.

In some embodiments, the source interface further comprises a numerical indicator associated a known source of the known sources that represents a number of new types of wellness data that can be provided by the known source.

In some embodiments, processing unit 5404 is further configured to: detect (e.g., with detecting unit 5416) a selection of a known source from the displayed list of known sources; and in response to detecting the selection of the known source, enable display (e.g., with display enabling unit 5414), on the display, of a list of types of wellness data that the known source can provide.

In some embodiments, the list of types of wellness data that the known source can provide comprises a selectable option for each of the types of wellness data that the known source can provide to approve or reject the associated type of wellness data.

In some embodiments, processing unit 5404 is further configured to: detect a selection of the selectable option for a type of wellness data that the known source can provide; and in response to detecting the selection of the selectable option, approve or reject (e.g., with approving or rejecting unit 5420) the type of wellness data that the known source can provide in accordance with the detected selection of the selectable option.

The operations described above with reference to FIGS. 38A and 38B are, optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 54 . For example, receiving operation 3802 and identifying operation 3806 may be implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136. A respective event recognizer 180 of application 136 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub event, such as activation of an affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.

Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.

As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the delivery to users of invitational content or any other content that may be of interest to them. The present disclosure contemplates that in some instances, this gathered data can include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information.

The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure.

The present disclosure further contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. For example, personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection should occur only after receiving the informed consent of the users. Additionally, such entities would take any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices.

Despite the foregoing, the present disclosure also contemplates examples in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of advertisement delivery services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services. In another example, users can select not to provide location information for targeted content delivery services. In yet another example, users can select to not provide precise location information, but permit the transfer of location zone information.

Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed examples, the present disclosure also contemplates that the various examples can also be implemented without the need for accessing such personal information data. That is, the various examples of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content delivery services, or publicly available information. 

What is claimed is:
 1. An electronic device, comprising: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: determining whether a first user is authorized to access wellness data associated with a second user; in accordance with a determination the first user is authorized to access the wellness data associated with the second user, transmitting the wellness data associated with the second user to the electronic device of the first user; and in accordance with the determination that the first user is not authorized to access the wellness data associated with the second user: prompting the second user to authorize the first user to access the wellness data associated with the second user; subsequent to prompting the second user, receiving an input indicative of whether the first user is authorized to access the wellness data associated with the second user; in accordance with a determination that the input indicates the first user is authorized to access the wellness data associated with the second user, transmitting the wellness data associated with the second user to the electronic device of the first user; and in accordance with a determination that the input indicates the first user is not authorized to access the wellness data associated with the second user, forgoing transmitting the wellness data associated with the second user to the electronic device of the first user.
 2. The electronic device of claim 1, wherein the first user is a health care provider and the second user is a patient; and wherein the one or more programs further include instructions for: receiving, from the first user, a request to access the wellness data associated with the second user, prior to an appointment between the first user and the second user.
 3. The electronic device of claim 1, the one or more programs further including instructions for: prior to determining whether the first user is authorized to access the wellness data associated with the second user: receiving, from the electronic device of the first user, a request to authorize the first user to access the wellness data associated with the second user.
 4. A method comprising: determining whether a first user is authorized to access wellness data associated with a second user; in accordance with a determination the first user is authorized to access the wellness data associated with the second user, transmitting the wellness data associated with the second user to the electronic device of the first user; and in accordance with the determination that the first user is not authorized to access the wellness data associated with the second user: prompting the second user to authorize the first user to access the wellness data associated with the second user; subsequent to prompting the second user, receiving an input indicative of whether the first user is authorized to access the wellness data associated with the second user; in accordance with a determination that the input indicates the first user is authorized to access the wellness data associated with the second user, transmitting the wellness data associated with the second user to the electronic device of the first user; and in accordance with a determination that the input indicates the first user is not authorized to access the wellness data associated with the second user, forgoing transmitting the wellness data associated with the second user to the electronic device of the first user.
 5. The method of claim 4, wherein the first user is a health care provider and the second user is a patient; and wherein the method further comprises: receiving, from the first user, a request to access the wellness data associated with the second user, prior to an appointment between the first user and the second user.
 6. The method of claim 4, further comprising: prior to determining whether the first user is authorized to access the wellness data associated with the second user: receiving, from the electronic device of the first user, a request to authorize the first user to access the wellness data associated with the second user.
 7. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device, the one or more programs including instructions for: determining whether a first user is authorized to access wellness data associated with a second user; in accordance with a determination the first user is authorized to access the wellness data associated with the second user, transmitting the wellness data associated with the second user to the electronic device of the first user; and in accordance with the determination that the first user is not authorized to access the wellness data associated with the second user: prompting the second user to authorize the first user to access the wellness data associated with the second user; subsequent to prompting the second user, receiving an input indicative of whether the first user is authorized to access the wellness data associated with the second user; in accordance with a determination that the input indicates the first user is authorized to access the wellness data associated with the second user, transmitting the wellness data associated with the second user to the electronic device of the first user; and in accordance with a determination that the input indicates the first user is not authorized to access the wellness data associated with the second user, forgoing transmitting the wellness data associated with the second user to the electronic device of the first user.
 8. The non-transitory computer-readable storage medium of claim 7, wherein the first user is a health care provider and the second user is a patient; and wherein the one or more programs further include instructions for: receiving, from the first user, a request to access the wellness data associated with the second user, prior to an appointment between the first user and the second user.
 9. The non-transitory computer-readable storage medium of claim 7, the one or more programs further including instructions for: prior to determining whether the first user is authorized to access the wellness data associated with the second user: receiving, from the electronic device of the first user, a request to authorize the first user to access the wellness data associated with the second user. 